Yes, my opinion is it *will* use more heap memory when used under load and that needs to be configured, no matter what.
Maybe there is a bug in eucalyptus code that makes it consume much more memory than it should, and it should never be necessary to raise it over the default heap size. Maybe there is a bug in eucalyptus that makes it leak references to objects over time, and any value we put in will always not be enough after some time. But having that knob and documenting its use cannot hurt. Especially if upstream considers the memory usage profile under load to be "working as designed". -- walrus reports java.lang.OutOfMemoryError: Java heap space https://bugs.launchpad.net/bugs/565101 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
