From: Leif-Jöran O. <lj...@ex...> - 2012-09-29 12:08:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 2012-09-27 23:20, Wolfgang Meier skrev: >> Could you recommend a clean way to pass Xmx properties to the startup >> script, either when invoking build.bat or via a local build properties >> file? > > Leif's commit today changed the -Xmx setting. It used to be -Xmx512m, which is sufficient for a normal build. > Only running the test suite will need more. Just to make it clear, a forked test instance has its own memory setting: junit.forked.VM.maxmemory = 300m And also not to forget, for xslt and xqts we use the property junit.forked.VM.maxmemory.external (cut from build.properties): # Converted junit tests from external testsuites # reuire more memory, e g # XSLTS requires 512m # XQTS requires more than 400m junit.forked.VM.maxmemory.external = 512m So please use those for forked tests in local.build.properties if you run into memory problems with them. > We should set this back to 512. As promised yesterday I did set it to 512m for all 4 build.sh/bat instances. This will (only) change with the installer handling each installation memory setting separately or if you give it in local.build.properties (or similar property file) or on the commandline. Cheers, Leif-Jöran -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQZuS+hcIn5aVXOPIRApVMAJ4/iAAd7Dzsh7lQxYTBmhqzkih+YgCgi9gh WtkT4MXpSVROSftt3HO1du8= =EZjH -----END PGP SIGNATURE----- |