Hello, Which version of JMeter are you using ? Can you attach your test plan to a bugzilla or show a description of it ?
As for what you are saying, I have already used jmeter with a machine simular to the configuration you are describing and went up to 4000 threads and memory was not the limit in my case, so you should investigate your test plan first particularly if you are talking about Perm Gen as it's not the kind of memory that is highly consumed except if you are using Javascript for example. - What kind of Test Elements are you using ? - Are you using third party plugins? - Which listeners have you setup - Are you using XML or CSV output As for what you are saying regarding "*This is a frustrating problem which has been overlooked for a long time.*", please see: - http://wiki.apache.org/jmeter/JMeterPerformance Regards Philippe On Thu, Nov 29, 2012 at 8:40 PM, chaitanya bhatt <[email protected]>wrote: > Group, > > I have noticed that Jmeter uses unreasonable amount of memory per thread. > Even if you strip off loggers/result tree etc. you would still see a huge > consumption of memory. I monitored the Jmeter memory heap and tuned the JVM > as much as possible. In spite of this I noticed that the tenured generation > of the heap is always packed with objects of huge size. Lots of classes are > loaded dynamically which is causing high occupancy in perm gen. > > I am working on another home grown tool which uses HTTPClient library to > generate load. Using this home grown tool I can generate 4000 instances per > machine (64 bit with 32Gb ram and 16 CPU cores). But Jmeter on the contrary > fails to scale to a mere 1/10th of the target user load. > > This is a frustrating problem which has been overlooked for a long time. > > Can something be done about this? > > Thanks > Chaitanya M Bhatt > http://performancecompetence.com > -- Cordialement. Philippe Mouawad.
