While it is possible to imagine doing aggregation with memcache - maybe - it's very hard to imagine it being worth the effort. It's like using a hammer to punch staples - sure, it's possible, but you'll break a lot fewer fingers if you just use a stapler. How do you pick memcache keys for thousands of users that are constantly signing in and signing out? You can't just assign them 0-9999; you'd need some sort of coordination system to recycle empty spaces. And now you need that coordinator to scale because it rapidly mutates.
Memcache doesn't have a list structure. Really, if this was being done with off-the-shelf components, it's a good fit for Redis. But even that is overkill; a dozen-line Node.js script can accept HTTP directly from clients and works just as well. Jeff On Mon, Aug 13, 2012 at 3:53 PM, hyperflame <[email protected]> wrote: > On Aug 13, 4:43 pm, Hernan Liendo <[email protected]> wrote: >> MemCache.getAll(keys) method could work if you know the keys. Using sharded >> keys you could reach them all. > > I wrote a simple test application for memcache earlier. I managed to > collect 1k keys reliably for my simple test application, and I would > bet that 10k keys would be no problem. The problem is the amount of > data in the value. If you just wanted to store scores, that would be > fine, but IIRC the original poster needed to store a lot more data > than just scores. > > On Aug 13, 4:43 pm, Hernan Liendo <[email protected]> wrote: >> On Monday, August 13, 2012 3:10:17 AM UTC-3, Jeff Schnitzer wrote: >> > The problem is pretty easily stated: Collect 10k score submissions in >> > 5s and be able to provide a sorted leaderboard 5s later. GAE does not >> > offer any practical facility capable of accomplishing this. >> >> Yeah, that's right :( > > Personally, I'd like to see memcache made more reliable, and more > guarantees added to it (and I would have no problem paying more). > Right now memcache is "Well, it's there, but it could go out at any > time." > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
