Hello, Read this : http://jmeter.apache.org/usermanual/best-practices.html
Ensure you are not using View Results Tree or any other costly listeners. After checking all these points don't jump to conclusion that other parameters are OK if your original load test tool is reporting OK. Built-in samplers are rather highly tested and used , so i am not sure writing your own will help. Regards Philippe M. On Tue, Jul 24, 2012 at 8:28 PM, unjc email <[email protected]> wrote: > Hi all, > > I have a test plan with 100 threads of HTTP Request samplers hitting a > web server via proxy server. My goal is to hammer the server as fast > as possible for an hour. When I run the test for first 30 seconds, > the throughput is excellent; slowly I found it keeps dropping. I am > sure it's not a problem with the network, proxy or web server because > the other load-testing tool has been working fine before I switch to > try Jmeter. > > I found that Jmeter consumes lots of memory and cpu cycles during the > test. I have tried "Statistical" and "Stripped" mode, along with > 2048M heap size. Nothing really helps to keep the test running for > long period of time. The java process is one hungry monster in the > top stats. Is there any lighter sampler available (that supports > proxy, custom originating IP, and https)? If not, is there any good > document that could help start writing my own plugin? Any comment or > advice will be greatly appreciated. > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 6128 root 20 0 10.5g 2.3g 14m S 539.2 19.5 6:16.95 java > -server -XX:+HeapDumpOnOutOfMemoryError -Xms2048m -Xmx2048m > -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=2 > -Dsun.rmi.dgc.client.gcInterval=6 > > > > Thanks, > Jacky > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cordialement. Philippe Mouawad.
