you are not going to like this answer... every application is different.
the memory required is the memory required. if you need more, give it more.... or redesign the app. there are tuning tips to trade large stop the world gc pauses for fewer shorter pauses and increased heap fragmentation... but at the end of the day if the app reaches a point where to serve a request takes more memory than is available to the application, then you need to give it more memory or redesign the way it handles the request. sorry. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 19 Dec 2011 20:01, "Jim May" <[email protected]> wrote: > I have been doing some research on this topic and I know that there is > quite a bit of information out there. Unfortunately, I usually do not > notice articles that recommend JVM tuning setting for servers with X amount > of memory. I have an issue with a production tomcat server that is running > two applications. One of the applications has an export all records feature > AS AN OPTION. The default is export only the 100 rows on the page, but > sometimes the Admin needs to go to the site and export all records into > excel for their reporting. Now the admin is triggering the export all > feature and the server is imploding with out of memory errors for the heap. > > This is the current settings: > > -Xms256m -Xmx1024m -XX:MaxPermSize=384m -XX:PermSize=256m > > I was wondering what you would recommend for JVM tuning settings on a > server that has 8GB or higher of memory? Are there rules that are usually > followed in deciding the settings? The server is completely dedicated to > the two websites and the database runs on a different server. > > Thanks, > -- > James >
