Wade Chandler <[EMAIL PROTECTED]> wrote: > > Sometimes changing the ratio to not have enough new > space and then creating too many objects too fast can > make your application eventually throw OOMEs because > it can't move the objects into older spaces quick > enough depending on what you application is doing.
Gosh, it looks like "don't move your mouse coursor to quickly or your operations system will fail" :D > How much memory does your system have compared to how > much memory you have allocated to your heap? Asking > because of the way the VM will be able to allocate > memory. The total heap size switches are separate > from the MaxPermSize, so if your heap size is too > large and then you have bumped up your PermSize then > you could have this issue when your PermSize resizes > and your heap tries to grow as well. MaxPermSize > doesn't set the PermSize to that size, but is merely a > limit, so it will grow as you add to your permanent > objects (classes and statics). phisical: 3gb settings: -XX:MaxPermSize=512m -Xms1024m -Xmx1024m (was 256m for Perm, 512m now) -- T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
