News for hackers. Stuff that matters.
Re:This is what 864GB of RAM looks like now by robotresearcher on Friday January 27, 2012 @12:32PM (#3519145)
Does memcached not use virtual memory?
Re:This is what 864GB of RAM looks like now by danudey on Friday January 27, 2012 @01:54PM (#3519553)
Memcached is designed to be fast. Anything that makes it slower that doesn't need to be there isn't there. For example: authentication (anyone who can access the port can fetch data), indexing (you need to know the key), deallocating memory (you configure memcached with an upper bound; it keeps allocating memory as needed until it gets there), etc.

Virtual memory (I assume you actually mean 'does memcached not page data out to disk') would make it much slower. Since memcached is just that - a memory cache - if you're out of memory it just expires the least-recently-used data. In your application, you fetch the key, and if that fails you fetch it from the primary data store (or wherever else you can find it).

Re:This is what 864GB of RAM looks like now by TylerE on Friday January 27, 2012 @01:42PM (#3519483)
In theory it probably could, but you're losing all benefit at that point. The big selling point of memcahce is that it's VERY fast. Our memcache server (Ours is only 8GB, not nearly as impressive as some) averages under 1ms object fetch times, even accounting for network overhead.
Re:This is what 864GB of RAM looks like now by wmf on Friday January 27, 2012 @01:34PM (#3519453)
IIRC memcached is event-driven and swapping is death for event-driven programs because it blocks the whole event loop.