I've often seen comments about using multi-gets for better performance. First, I'm a bit curious if/why it's a big performance gain. Obviously, not all keys will be on the same memcached server in a multi-get request. Can somoene give me the one short explanaition or point me to where to learn more?
I'm perhaps more curious how people use multiple gets -- or really the design of an web application that supports this. I've tended to cache at a pretty low level -- that is if I have a method in the data model to fetch object "foo" I tend to check the cache, if not found then fetch from the database and save to memcached. As a result we can end up with a lot of separate memcached get requests for a single web-request. This is less true as the app becomes more web2.0-ish, but still happens. So, I'm curious about the design of an application that supports gathering up a number of (perhaps unrelated) cache requests and fetch all at once. Then fill in the cache where there are cache-misses. Am I misunderstanding how people use this feature? -- Bill Moseley [email protected]
