You're right. it could be a problem with his test plan, but without seeing the test plan it's hard to know. Even if his test plan is correct, testing SSL/HTTPS is still very hard to do. Unless the hardware resources are available, it's just very hard to simulate HTTPS traffic effectively and accurately.
peter On 5/11/05, Scott Pack <[EMAIL PROTECTED]> wrote: > Peter, > > I presume you are speaking to the system under test. I believe the issue Elli > is reporting is with JMeter. I have had this same problem with a test where > JMeter failed after 25 iterations of a fairly complex script. Only by > removing all the listeners was it capable of running to completion. > > Scott > > -----Original Message----- > Subject: Re: Out of memory error > > HTTPS is a tremendous CPU hog and will eat up plenty of RAM. In > general, a 2ghz CPU will max out with 20 concurrent HTTPS requests. > More than that, you're not really stressing the server. > > if you really need to test HTTPS, I would recommend keeping each > client machine to 10 threads. Most of the sites that require heavy > HTTPS use hardware accelerators. I personally don't recommend using > software HTTPS if the expected HTTPS load is more than 10-15 > concurrent. > > for example, a 450mhz P3 can reliably handle 3-5 concurrent requests. > More than that the server will crash. this is primarily a hardware and > IO limitation. > > peter lin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
