On Sun, May 18, 2008 at 2:32 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > 2 or 3. There are some sites that I'd like to run outside examples and > the 'production' instances. For example the teatime application will > receive some loving care soon and need some restarts. I'd like to do > that without affecting the 'production' apps that drive our community > (also without having to wait for 2 minute while jira, confluence et al > start up). > > I do see that we are still limited in the amount of memory we can > claim for each vm. I'd do the following partitioning: > > - jira/confluence/teamcity/maven repo : 768MB > - wicket examples: 512MB > - teatime/other apps: 256MB > - teamcity build agent: 768MB > > Total: 2304MB > > This leaves 768MB for OS level stuff, such as file sytem cache, databases, > etc. > > Sounds reasonable?
I think that sounds reasonable. I guess we'll just have to see how it performs.
