Re: testing availability of a http server using WWW::Mechanize and multiple proxies

I'm a bit confused on what you really want.
You are mentioning a lot of concurrent accesses to the remote site, so maybe you do not want to check its availability but its performance.

If that is the case, I'd not recommend Mechanize for that task, there are tools that you can use, like Apache Benchmark or JMeter.

To check for the availability of the server you can do less frequent requests, and for this it does not really matter if you use Mechanize or just LWP.

Comment on Re: testing availability of a http server using WWW::Mechanize and multiple proxies

Replies are listed 'Best First'.
Re^2: testing availability of a http server using WWW::Mechanize and multiple proxies by spx2 (Deacon) on Jan 21, 2008 at 15:54 UTC
Hi, Thank you for replying. I knew of Apache Benchmark, but I want to learn how to make something similar myself.That is why I've asked. How would you design such a tool ?	[reply]
Re^3: testing availability of a http server using WWW::Mechanize and multiple proxies by olus (Curate) on Jan 21, 2008 at 16:11 UTC
Take a look at HTTPD::Bench::ApacheBench. I've never used it so I can't say if it really is up to the task. Alternativelly, you can make the requests yourself using LWP. Since you only care to check is the response is 200 OK, there is no overhead in parsing the response.	[reply]