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


On 5/10/05, Elli Swift <[EMAIL PROTECTED]> wrote:
> Hi all,
> 
> I am load testing an HTTPS application and I'm continually running into this
> out of memory error:
> 
> [GCException java.lang.OutOfMemoryError: requested 8208 bytes
> 
> The garbage collection comes along but just doesn't seem to be clearing out
> enough room.  I have increased the heap size to 1024, I'm running jmeter on
> a server with almost 6GB of RAM, I have no listeners in my test, I'm running
> in non-gui mode and I'm only running a test with 25 users looping 4 times
> through (it dies almost immediately after the second loop finishes).
> 
> I created my script using the HTTP proxy server (I was able to disable HTTPS
> in order to record the script) and I noticed that it recorded quite a few
> things in each of the Browser-derived headers for each HTTP request.
> (If-None-Match, Referer, Host, Accept-Language, User-Agent,
> If-Modified-Since, and Accept).  Could any of these be using up unnecessary
> resources?
> 
> This truly puzzles me, as we were able to create a load test script for one
> of our other (non-HTTPS) applications and fire off close to 250 or 300 users
> and leave it running for hours without any problems.  Any suggestions would
> be very helpful!!
> 
> Elli
> 
>

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

Reply via email to