On 02/12/2011, at 9:20 AM, Peter Niederwieser wrote: > we now have basic support for setting JVM options for the daemon VM. > Initially I wanted to reuse the GRADLE_OPTS environment variable so that > this variable would take effect for whichever VM actually runs the build. > However, it's not easy/desirable to figure out from the client VM's startup > script whether the build runs in daemon mode or not. Hence I've introduced > another environment variable GRADLE_DAEMON_OPTS that just takes effect for > the daemon VM. > > What do you think about this solution? Do you have a better idea?
It doesn't quite strike me as right, but I'm not sure I have a better idea. One thing to consider is that there is going to be other daemon related configuration that is not just the JVM startup options. Right now there is the idle timeout configuration, but we may need things like idle pool size, max pool size etc. I wonder if something like ~/.gradle/daemon/daemon.properties might be a better fit. > Another question is whether we should set a default for GRADLE_DAEMON_OPTS, > in particular with regard to memory settings. Currently we don't, just as we > don't set a default for GRADLE_OPTS. We have up until now run with default memory settings though. > I'm a bit hesitant to add a "hidden" > default. Maybe it's better for memory settings to be configured explicitly > (or fall back to JVM defaults). What are the JVM defaults? From memory they aren't very generous for Sun JVMs. I don't necessarily have a problem with defaults if they are documented and explained to the user via a good error message if the daemon OOMs. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
