----- Original Message ----- > > > > > On 02/12/2011, at 3:33 PM, Peter Niederwieser <[email protected]> > wrote: > > >> 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. > >> > > > > I'm more concerned about the opposite: Wasting memory by setting > > high > > defaults in an attempt to prevent OOMs for most users. > > I don't think this is much of an issue. The OS will page out the > unused JVM heap. >
Sorry but I beg to differ. That's certainly not my experience (on Linux). As soon as I see any memory spilling over into swap, performance really goes down the drain fast. I don't think the JVM heap is really all that friendly/amenable to virtual memory management. Not to mention that if swap is in use, you don't get much memory being allocated to OS-level file caches, I notice that this has a major impact on startup times for something like Eclipse / STS (for re-starts, initial start isn't impacted as much). I didn't do any systematic testing, this is just from casual observation while working with Gradle/Eclipse and keeping an eye on my memory usage. Nevertheless, please don't make light of memory usage thinking that 'it is free', it really is not free. > Side thought: I wonder if we should call System.gc() after a daemon > build. No... calling gc is probably a bad idea. Especially if swap is being used. It will cause massive paging. Kris > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
