L, 09 apr 2011 kirjutas Tushar Chavan :
now when I do
./ab http://webdispatcher.domain/irj from apache server, I get
below error
Benchmarking webdispatcher.domain(be patient)...apr_poll: The
timeout specified has expired (70007)
Error in file error_log is as below.
Connection ti
Hi Jeff,
SSL session cache is utilized maximum as out of 3 requests 29850
requests was served as "session reuse" during my stress test
Thanks
On Fri, Apr 8, 2011 at 10:06 AM, Jeff Trawick wrote:
> On Wed, Apr 6, 2011 at 11:09 PM, Ishita Kapadiya wrote:
>> Hi Jeff,
>>
>> both ab and JMETER
Try this settings -
1)
StartServers20
MinSpareServers 20
MaxSpareServers 50
ServerLimit 1000
MaxClients 1000
MaxRequestsPerChild 10
2) As Jim suggsted - Timeout should be maybe 10 and KeepAliveTimeout
maybe 3. increase MaxKeepAliveReque
Dear List,
This is cached by mod_disk_cache:
http://www.t1shopper.com/mod_disk_cache_bug/index.php
This isn't cached:
http://www.t1shopper.com/mod_disk_cache_bug/
Anyone know what might cause this?
Thanks,
Geoff
---= Log showing page being written to host's cache =---
mod_cache.c(131): Addin
According to the apache documentation for mod_alias
"First, all Redirects are processed before Aliases are processed, and
therefore a request that matches a Redirect or RedirectMatch will never
have Aliases applied."
Without the trailing slash, the web server applies the slash and sends a
redirec
I tried different combination of the ServerLimit and MaxClients, as well as
setting higher the timeout for keep-alive requests.
StartServers10
MinSpareServers 10
MaxSpareServers 20
ServerLimit 1000
MaxClients 1000
MaxRequestsPerChild 1
The timeout values (both Timeout:120 and KeepAliveTimeout:15)
are obscenely large. Timeout should be maybe 10 and KeepAliveTimeout
maybe 3 (if a persistent connection is coming, it will come quickly,
otherwise its best to put up with the overhead of socket teardown/
buildup rather than have an Apac
> I tried to increase the ServerLimit and MaxClients directives, but it does
> not improve the test (or at least the numbers I tried). If I change the test
> to be done with HTTP 1.0, then the test is done perfectly, without any
> error. And if I reduce the waiting time between requests the test co
Hi,
I am testing Apache HTTPD (2.2.17) with a benchmarking tool called Tsung.
Apache is running the default configuration files, in prefork mode.
The keep-alive is configured as follows:
Timeout 120
KeepAlive On