Hi Ricardo,
I found when I was doing my tests with httperf, I had to use multiple
computers to do proper load testing because HTTPERF couldn't handle sending
so many simultaneous connections. Through trail and error the best results I
got was using only ~400 simultaneous requests firing from the so
The error called "connreset".
This is a example.
Total: connections 1 requests 1 replies 8952 test-duration 136.478 s
Connection rate: 73.3 conn/s (13.6 ms/conn, <=9387 concurrent connections)
Connection time [ms]: min 1025.6 avg 38879.9 max 134963.6 median 33947.5
stddev 23360.4
Connect
ricardo13 wrote:
Hi all,
I'm submiting workload my web cluster using HTTPERF.
The result shows several errors about connection reset.
My doubt is, when happen connection reset ??
Can you paste the *exact* error messages that you are seeing ?
Hi all,
I'm submiting workload my web cluster using HTTPERF.
The result shows several errors about connection reset.
My doubt is, when happen connection reset ??
Ricardo
--
View this message in context:
http://www.nabble.com/Connection-Reset-tp25690236p25690236.html
Sent from the Apache HTTP
On Sep 30, 2009, at 15:47 , Clive Kinton wrote:
Has anybody run into some weirdness with Apache 2.2.12 from Xampp on
Vista and ip to hostname resolution for 'localhost'? The httpd.conf is
vanilla, as shipped.
Specific issue: Trying to limit access to a directory with a
simple .htaccess file li
On Sep 30, 2009, at 12:32 , Alexander Müller wrote:
Hi,
we are having the following RewriteRule entry configured
RewriteRule ^/(.*)$ https://HOSTNAME/$1 [P]
which generally seems to work, all incoming requests are forwarded
to the indicated machine, not as redirect but utilising mod_prox
Has anybody run into some weirdness with Apache 2.2.12 from Xampp on
Vista and ip to hostname resolution for 'localhost'? The httpd.conf is
vanilla, as shipped.
Specific issue: Trying to limit access to a directory with a
simple .htaccess file like:
Order deny,allow
Deny from all
Allow from local
Hi,
I noticed the following warning text in the graceful-stop section of the
apache manual (http://httpd.apache.org/docs/2.2/stopping.html):
"You should also be wary of other potential race conditions, such as using
rotatelogs style piped logging. Multiple running instances of rotatelogs
attempti
Hi,
we are having the following RewriteRule entry configured
RewriteRule ^/(.*)$ https://HOSTNAME/$1 [P]
which generally seems to work, all incoming requests are forwarded to the
indicated machine, not as redirect but utilising mod_proxy.
The problem starts to occur when a URL contains a qu