a point... a query like select * from session_table where session_id='xxxxx' where session_id is a primary key is very very fast, we are talking about < 0.1 seconds, with memcached you are trying to go down to <0.01 seconds why should you care about speed in internet if the time to consider a page slow is near 3 seconds? you could use database without problems when memcached goes down and a simple query (in primary key) isn't database intensive, some guys use a mysql table per session when session ends DROP TABLE session_xyz this make the system more proof of broken engine (that don't work fast with frequently delete+update+select queries) other option is a session_table with many partitions, just some ideas..
2012/10/22 Perrin Harkins <per...@elem.com>: > On Mon, Oct 22, 2012 at 5:09 AM, SAE <simsimil...@googlemail.com> wrote: >> But as explained above. If one of the memcached servers goes down. Some >> users experience the problem, that they not only get logged out but also >> have problems browsing the site at all or logging back in. Every page needs >> minutes to load then and it seems like the client is still trying to reach >> the server that got down and he's not trying that for only the first few >> clicks after one server went down, but for every click after that. > > That sounds like an issue with your memcached client, rather than the > server. See if there's a mailing list or other support for the client > you're using. > > - Perrin -- Roberto Spadim
