On Thu, May 2, 2013 at 2:21 AM, Romain Manni-Bucau <[email protected]>wrote:
> thinking to it, we had a bunch of enhancement regarding tld scanning > caching which could explain a part of it + a better scanning for rest part > (i was testing a rest app) > > that said 33M vs 40M after GC sounds not aweful for a faster startup and a > more consistent runtime > > Okay, I've made some changes in my configuration. 1. Of course, still using last/latest TomEE 1.6.0 snapshot (2013-04-29 version) that I downloaded 2. Reverted to Atmosphere 1.0.12, because I found that a stable version and I really did not need Atmosphere 1.0.13 'snapshot' at all. 3. Increased -Xms/-Xmx from 1250m to 3000m, since I recognized latest TomEE 1.6.0 snapshot (OWB 1.2) seem to 'use' more memory; 600m x 5 = 3000m (lowest memory required to run app x 5, as recommended on tomcat list); i 'assumed' that my app requires 600m, since I usually see memory used = 600m most of the time I login to production server and check heap/memory used via jvisualvm With all that said, * screen capture[1] shows memory-used above 800m; this was few minutes after I stopped doing some heavy lifting (or activity) in web app * screen capture[2] shows that memory-used dropped to approximately 140m (evidently, due to some GC) So, based on all this, should I keep -Xms/-Xmx at 3000m or decrease it to 1250m, as I had it set to that earlier? FWIW (and from what I remember), my web app has never experienced an OOME. On my development server, I think I set -Xmx to 512m and -Xms may be 256m, and I never experience any issues starting/testing/stopping the web app. [1] http://imageshack.us/a/img23/5043/20130504jvisualvm1.jpg [2] http://imageshack.us/a/img11/2079/20130504jvisualvm2.jpg
