On Mon, Jul 23, 2018 at 07:03:16PM +0200, Duy Nguyen wrote: > > > Try bumping core.deltaBaseCacheLimit to see if that has any impact. It's > > > 96MB by default. > > > > > > There may also be some possible work in making it more aggressive about > > > storing the intermediate results. I seem to recall from past > > > explorations that it doesn't keep everything, and I don't know if its > > > heuristics have ever been proven sane. > > Could we be a bit more flexible about cache size? Say if we know > there's 8 GB memory still available, we should be able to use like 1 > GB at least (and that's done automatically without tinkering with > config). I have mixed feelings on that kind of auto-scaling for caches. Git isn't always the only program running (or maybe you even have several git operations running at once). So in many cases you'd want a more holistic view of the system, and what resources are available. The OS already does OK scheduling CPU and the block cache for our mmap'd files. I don't know if there's a way to communicate with it about this kind of cache. I guess asking "what memory is free" is one way to do that. But it's not always the best answer (because we might be happy trade off some block cache, etc). On the other hand, that would always give us a conservative value, so if we picked min(96MB, free_mem / nr_cpu) or something, that might be an OK rule of thumb. -Peff
