RFR: 8014510: Fix sjavac on all platforms in jprt
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Fri Aug 29 11:11:21 UTC 2014
On 2014-08-22 16:20, Erik Joelsson wrote:
> Thanks for looking into this. I took the liberty of tuning this some
> more and finally arrived at this set of changes:
> First of all I wanted to get rid of the big if-else construct, so I
> changed that into a simple MEMORY_SIZE/2 for sjavac server mx flag.
> Then I did some tests on my machine and with the modules build, sjavac
> really isn't that memory intensive anymore. I set a cap at 2GB (1,5
> for 32 bit jvms) and also set a minimum of 512M, which I have verified
> still works. I also removed the verbosegc flag.
> When changing these settings, it struck me that the mx in
> BIG_JAVA_FLAGS is a static configuration and should probably also be
> tuned in the same way. I left the old values as the maximum caps and
> let them go as low as 512. This has also been verified to be enough.
> Finally, since the memory requirements of the java instances in the
> build have been reduced, I also chose to tweak the memory based
> limiter on the default number of jobs.
Looks good to me.
More information about the build-dev