On 10/25/2012 02:00 PM, Eugene Gorelik wrote: > Number of CPUs used by the app depends on the thread control in the app > itself or in the application container where this app is deployed. > > Amount of used memory heap depends on the number of objects which are > loaded to the memory. Garbage collection process is regulated by JVM and I > don't think it is possible to manually set GC interval. > Therefore it is difficult to predict exactly when GC happens and to prevent > JVM from memory clean-up. > As always, you can experiment with putting load to the app and see how it > behaves. > > if you think that problem is related to memory leak, then take a java heap > dump and analyze it using tool like IBM heap analyzer: > http://www-01.ibm.com/support/docview.wss?uid=swg21190608 > > Working closely with developer of the app should help a lot. > Unfortunately, the developer is in the Netherlands. In this particular situation, the guys working on the specific problem do speak to the developer frequently because this is an ongoing project with a rather ambitious time frame. So, in this case, we have a guy here who is 100% dedicated to this client problem with 3 VMs. Yesterday we ran into a "too many Open Files" issue. That is an easy one to solve, I bumped up the soft and hard file limits.
-- Jerry Feldman <[email protected]> Boston Linux and Unix PGP key id:3BC1EB90 PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
