[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jgit-dev] jGit memory management and optimizations
- From: Shawn Pearce <spearce@xxxxxxxxxxx>
- Date: Sun, 25 Nov 2012 11:39:42 -0800
- Delivered-to: email@example.com
On Sat, Nov 24, 2012 at 10:45 PM, <emilian.bold@xxxxxxxxx> wrote:
>>> It's not about releasing the memory back to the OS, it's about just not using so much of it. Ideally I would like some way to configure jGit to only cache 100MB in RAM and re-load/re-compute cache misses.
>> That's a nice dream. Not sure you can get there without making it so
>> slow that its unusable. Try getting more RAM, its fairly cheap these
>> days. Its not like we are still in the 640 KiB is enough for anyone
>> days of DOS.
> Oh, I have more than enough RAM. But for an application that runs nicely with -xmx 200MB it's a bit odd that adding jgit means I have to raise that another 500MB just to be certain it doesn't OOME on a large git repository.
> Thank you for your feedback.
> Since this problem seems hard to fix I'll lower its priority and just take jGit as it is.
I'd love to see this improved, I was just trying to warn you that
people have tried and have not yet been successful. Hopefully someone
will have some new insight one day that will offer a significant
improvement. The bitmap based enumeration for packing came about as an
accident as we were exploring ways to improve branch level access
controls in Gerrit Code Review. :-)