in reply to LWP over SSL Hammers Apache


That is very interesting, real world browser and proxy caching is pretty hard to account for.

We have been doing similar load testing by using fork and creating system calls direct to lwprequest.

We found that our test script was limited to creating about 600 parallel requests this way, apparently by the server processing power.

I was just wondering how many concurrent requests you have managed to generate using this module.

I am assuming that calling lwprequest directly will allow more parallel requests to be generated than the overhead of using the perl interfaces like this. What do you think is the best way to generate the most parallel requests?