Is your feature request related to a problem? Please describe.
It is really needed? Why not load commits by chunks by, for example, 100-500 commits (TortoiseGit does that) when you scroll. I have a repo with ~300000 commits and sometimes I want to search in history of a file that rarely changed. I have to increase the overall graph depth just for that. That have impact on memory. For example, 10000 requires about 1.5 GB (tolerably), but 50000 already 5-6 GB. Most of the time I do not need such deep graph, but sometimes I want to see the history in context.
Describe the solution you'd like
Get rid of the setting. Read commits by chunks in maybe 100-500 commits per chunk. Keep as many commits as possible by SoftReference
Describe alternatives you've considered
Increase setting, but this is not good for memory and latency.
Is your feature request related to a problem? Please describe. It is really needed? Why not load commits by chunks by, for example, 100-500 commits (TortoiseGit does that) when you scroll. I have a repo with ~300000 commits and sometimes I want to search in history of a file that rarely changed. I have to increase the overall graph depth just for that. That have impact on memory. For example, 10000 requires about 1.5 GB (tolerably), but 50000 already 5-6 GB. Most of the time I do not need such deep graph, but sometimes I want to see the history in context.
Describe the solution you'd like Get rid of the setting. Read commits by chunks in maybe 100-500 commits per chunk. Keep as many commits as possible by
SoftReferenceDescribe alternatives you've considered Increase setting, but this is not good for memory and latency.