Hi PeterJ, Thanks for the response I appreciate it. In case you did not notice I mentioned that the heap should be adjusted to meet the needs of the application and the settings I mentioned were for my own application. What I hopefully pointed out also that the main emphasis is on getting the CPU to not be busy resizing the tenured and new generation areas. The developers/leads should always measure then measure again the performance gains for each setting under varying loads. I have done this and have made great gains on production systems over the years following this process.
One of my goals was to avoid major collections which I was able to do since the objects were very short life span (message objects for interfaces mainly). Other applications will probably have singletons or caches which I expect would end up being tenured so what you say would be true. I would be interested in seeing any reseach papers you have written since papers do have great ideas. Even though I see on the web the message heap sizes depends on application usage it is really true. Again thanks for the feedback. -Tony View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950484#3950484 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950484 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
