Little clarification needed about using a profiling tool during load testing the applications
Am using JProfiler for profiling my application. using weblogic 9.2 server. I want to look into memory consumption of my application since its taking too much memory during execution (load testing) and too much GC will occupy CPU time as well. So i tried memory profiling with jprofiler 6.2.2 on my application. For a single run its fine. But what i really want to test is that how the memory looks when server is under load, which am not able to because the JVM is crashing every time i start load testing with profiler. Am using webload for load generation.
My doubt is should profiling tool be used during heavy load testing of application ? If yes, then what am i doing wrong because of which my JVM is crashing.
my approach would be to switch GC to verbose mode, have it writing to a file and analyze the file after the load test run.
Will be one file per Managed Server and I cannot quote any Java command line options as they are vendor specific.
Are you using JRockIt, HotSpot, IBM or else?
Am using Jrockit. I want to analyze the Heap behavior under load. I'll try the verbose mode and see if i can get more information about heap usage. I wanted to use jprofiler during load testing because it'll be easy to analyze the results and interpret the same.
Time is mother nature's way of keeping everything from happening at once. And this is a tiny ad: