Hello,
We have four separate memcached instances serving our production website.
Below is the configuration of the instances in the web.config.
<enyim.com>
<memcached>
<servers>
<add address="<SERVER 1>" port="11215" />
<add address="<SERVER 1>" port="11216" />
<add address="<SERVER 2>" port="11215" />
<add address="<SERVER 2>" port="11216" />
</servers>
<socketPool minPoolSize="10" maxPoolSize="240"
connectionTimeout="00:00:03" deadTimeout="00:00:15" />
<locator type="RDA.Caching.EnyimCustomizations.CustomNodeLocator,
RDA.Caching.EnyimCustomizations" />
</memcached>
</enyim.com>
Yesterday, we set up a Memcached monitoring solution, and we noticed the
rate of gets/min and hits/min is quite a bit higher on the "*<add
address="<SERVER 1>" port="11215" />*" instance compared to the other
three.The rate of Sets/min are balanced across the instances, as are some
of the other metrics (e.g. connections, threads, etc.). We have enabled
logging via NLog and diagnostic logging in the past as well, and the only
out of the ordinary thing we see in the log is an occasional dead pool, but
that isn't consistent across any one instance.
Has anyone seen this behavior in their experience? We are currently using
version 1.4.4-14 of the memcached.exe
Thanks,
Sheel Shah
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
