Luke Daley-2 wrote > > The issue at hand is how to think about default settings for memory usage, > particularly heap. If we are going to provide defaults, we'll have to > either be conservative to avoid the JVM using too much memory or be more > generous to allow the defaults to be more useful for more builds. > I hope you can be interested in a use case: imagine the poor man developing the GWT UI for a web application. His memory should be enough for the following JVM instances: - the IDE (i.e. STS with its great Gradle integration) - the Gradle daemon (at least for the IDE) - an Apache Tomcat - the GWT DevMode for java-to-js on the fly translation
With huge xmx/maxpermsize defaults the poor man (me) ends up swapping all the time, even with 4GB of ram!!! Just my two cents -- View this message in context: http://gradle.1045684.n5.nabble.com/Setting-JVM-options-for-daemon-VM-tp5041975p5054754.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
