What is the limit of maximum connection (-c)? Is there any drawback
for setting it too high?
Currently our worker settings are
IfModule mpm_worker_module
ServerLimit 40
StartServers 10
MaxClients 2000
MinSpareThreads 500
MaxSpareThreads 2000
ThreadsPerChild
I am using the stable 2.x one. I have set the timeout to 3 secs now. Lets
see how that goes
Snehal
On Sun, Jul 11, 2010 at 10:33 PM, dormando dorma...@rydia.net wrote:
On Sun, 11 Jul 2010, Snehal Shinde wrote:
Yes Jay is right. My server and client config are in sync. The problem
is
On Mon, 12 Jul 2010, Snehal Shinde wrote:
I am using the stable 2.x one. I have set the timeout to 3 secs now. Lets see
how that goes
Snehal
You might want to stick with 2 or 4 seconds to test :) putting it right on
the line with the SYN timeout will still give you inconsistent results...
switched to 4 secs now. also if its a packet loss issue will it make sense
to reduce the $retry_interval from the default 15 secs to say 2 secs?
http://us2.php.net/manual/en/memcache.setserverparams.php
also the error that i get intermittenly is COULD NOT CONNECT TO SERVE. Is
there a way to find
Hey all,
Writing again about my changes to memcached-tool - never got a reply
to the first message, but here are the highlights:
1) Search
Added an option to search by key or value
2) Delete
Added an option to delete by key
This is particularly useful on a production system if you want to
What is your pageview velocity? There's really no good reason you should be
seeing intermittent failure and having timeouts that high will impact your
pageload performance.
As was mentioned, if you're seeing behavior like this you ever have serious
network or server hardware/configuration issues
switched to 4 secs now. also if its a packet loss issue will it make sense to
reduce the $retry_interval from the default 15 secs to say 2
secs? http://us2.php.net/manual/en/memcache.setserverparams.php
also the error that i get intermittenly is COULD NOT CONNECT TO SERVE. Is
there a way
