Andrea Aime wrote: > Hmmm... let's make the default pom use 256MB then? ;-)
That would be better than the current discrepancy. > Seriously, we may look in having the build server use more memory for > some time (mind, this may well end up having the build server go in > a swap storm as a result) but I really feel a plan to avoid GS becoming > more of a memory hog should be on the table. Perhaps we make them both 512M for now and give us a few weeks to put the app-schema unit tests on a diet? We have three options (not mutually exclusive): (1) Update EMF to a later, more efficient version. (2) Gabriel's suggestion of not parsing absolutely everything. (3) One-time test setup and read-only resource sharing between tests. Between them, these should be able to remedy the bloat. Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
