Answer by RuotsalainenI for Memcached best practices - small objects and lots...
I would say you should store values individually and use some kind of helper class to retrieve values with multiget and generate a complex dataobject for you.
View ArticleAnswer by santiagobasulto for Memcached best practices - small objects and...
It depends on what are those numbers. If you could, for example, group them in ranges, then you could optimize the storage. If you could hash them, into a map, or hashtable and store that map...
View ArticleAnswer by Domas Mituzas for Memcached best practices - small objects and lots...
I wrote somewhat large analysis at http://dammit.lt/2008/12/25/memcached-for-small-objects/ - it outlines how to optimize memcached for small object storage - it may shed quite some light on the issue.
View ArticleAnswer by Nate for Memcached best practices - small objects and lots of keys...
It depends on your application. While memcached is very fast, it does require some request transmission and memory lookup time per request. Those numbers increase depending on whether or not the server...
View ArticleAnswer by Alex for Memcached best practices - small objects and lots of keys...
I would say lots of little keys. This way you can get the exact result you want in 1 call with minimal serialization effort. If you store it in another object (an array for example) you will have to...
View ArticleAnswer by jrockway for Memcached best practices - small objects and lots of...
The less processing you have to do of the cached values, the better. So why not just dump them into the cache individually?
View ArticleMemcached best practices - small objects and lots of keys or big objects and...
I use memcached to store the integer result of a complex calculation. I've got hundreds of integer objects that I could cache! Should I cache them under a single key in a more complex object or should...
View Article