W dniu 07.01.2011 23:24, Nikolaos Giannopoulos pisze: > So... 512M + 200M + <?>... should at least be 712M+ and 800M isn't a > surprise. > > What are you doing when you see it go up to 1.5G? Does it happen over a > protracted period of time? Perhaps a NetBeans memory leak? If its > nothing special then I would look at bug reports and consider switching > to another IDE as 1.5GB is ridiculous.
Right now it's taking up 901M and it was just "idly" sitting there since I sent last post. You are right that it's ridiculous, but alas migrating to Eclipse or other IDE is not that easy, especially when Metisse has been used in app client. > What exact version of GlassFish and what JDK? v3 Final? 1.6_? I have not > seen any such memory leaks... . Do you happen to have a .hs_err_BLAH > (IIRC the name) file when the OOM occured... b/c if you do then you > should be able to easily see what filled up... if it indeed was perm gen > space or something else? I've had it on 2.0 and 2.1, I have it on 3.0 final. Always using the newest 1.6 JDK. I remember seeing some hs_err files, will see what's inside. > It's quite common practice to have on production app servers the min and (...) > periodically and review the data. Those are really nice tips, thanks. > What OS are you running on and what is your -Xss JVM setting? On Solaris > for example 1MB is allocated to the stack for each thread which is > overkill for almost any production app... 128k is typically more than > sufficient. I'm on 64-bit Ubuntu Linux 10.10 now. We see the same problems with the NB-GF duo on Macbook Pro, I had the same unstability back in the days I used Windows. I got used to that I guess. > Performance tuning is a big area in itself and there are many things to Yeah, we were able to increase the number of simultanous user sessions production server can handle 3-fold just by tuning some Glassfish options. > But honestly you can't compare any app server in development vs. > production as the load characteristics and most often even the OS aren't > even the same. For me it's the same OS, same JDK and same most of the software environment. What's different is hardware of course and load characteristics, but I am observing that production Glassfish _also_ fails when "too many" redeploys are done. Unfortunately, during development there are sometimes several redeploys per minute (thanks to deploy on save feature in Netbeans). > I think that pretty much covers the hardware side... save of course a > big screen and / or external display. Probably will go with Dell Vostro 3700 with i5 and 8 gigs. Thanks for insights to everyone. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
