1.4 JDKs have a pretty serious performance bug in the URL.encode method. You'll run much MUCH faster if you use JDK 1.3 or you don't encode your parameters, etc.

Salut,

Jordi.

Barry Roberts wrote:
I have a script that exercises a servlet-based application (running on Tomcat).  I would like to do some massive multi-user tests, but on Windows 2000, just running 35 threads runs the machine out of memory.  I do have -Xmx384m added in the jmeter.bat file, otherwise the JVM runs out of memory.

Should it really take that much memory (this machine is a dual PIII with 512M and not really doing much else)?  The script has a cookie manager and an aggregate reporter, and all the rest is just html samples recorded using JMeter proxy.  This machine is Win2k, JMeter 1.8 J2SDK 1.4

The same script pretty much maxed out the CPU on a Dual P4 1.7G at 20 threads under RedHat 8.  Don't remember how much memory was used, but it was a lot.  Am I doing something wrong or is 20 threads about all I can do per machine with JMeter?

I can send the script (it's about 37K zipped) if that would help.

Thanks,
Barry Roberts






--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to