> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: Effect of Heap Size on Performance? > > A smaller heap means that you'll catch even small memory leaks faster.
Good for debugging, but provokes more frequent GCs, so may not be optimal for production. I tend to use the largest heap that will avoid paging; this is often difficult to determine, unless the system you're running on is used only for the one Java application. > Granted, a larger heap invites more objects into it The above requires clarification: the max size of the heap has nothing to do with the number of persistent objects the application creates - that's purely a function of the app; the number of dead (unreachable) objects has negligible effect on GC time. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
