Hi Fred,
The problem is pretty general. I'm trying to learn a more scientific way to allocate memory for the JVM. Tweaking forever may very well be my fate.
My project is a
JEE data visualization app that uses a proprietary network protocol to display/analyze a huge (2PB and growing) data store.
Getting the data is a pretty slow operation so there is a series of cron jobs running on various schedules that maintain a mysql database that among other things acts as an index to speed searching.
I've been tweaking these programs to divide the problem into manageable chunks, but as the data grows the memory needs grows.
My reading suggests it's not a good idea to just assign as much memory as you have.
I wish I could be more specific but I don't have an acute problem, yet.
Joe