On Tue, 27 Jan 2009 20:13:59 +0000, Matthew Toseland wrote: > Memory usage was plateauing = memory usage was constantly at the > (low) maximum, and it was using 100% CPU in a vain attempt to reclaim > the last byte of memory. This is the most likely explanation by far
Right. (Is it just me, or does that sound like a design flaw with the jvm? Ie. if it is that short on memory, why doesn't it produce a graceful NotEnoughMemoryError, instead of killing my machine's cpu in search of the last free byte? > If it is a memory problem, db4o will probably solve it, however the > db4o branch does do somewhat more disk access, which might > conceivably be a problem on very old hardware. I hope so :S. It is pretty bad, atm, for machines with "little" free RAM. Any rough idea of when we can expect this?
