On Tue, Mar 9, 2010 at 9:45 AM, TheOnly92 <05049...@gmail.com> wrote: > We have been having problems with the memcache server storing sessions > data, the cache miss was about 20%, therefore we added in another pool > of memcache servers, but now the cache miss rate is up to 40%. We > adjusted the order of the memcache server pool, so that every web > server shares the same order, we also increased memcache memory up to > 256 MB, however still users are reporting continuous problems. What > could be the cause?
I don't know if I am understanding it right, but I'd say that memcached is not the right tool to store session data. What it is likely happening is that you have evitions (not enough memory to hold all the concurrent sessions) and memcached is dropping items from memory. You should not design an application which depends on data present in the memcached to work as expected. Carlos.
