Hi,

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?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.