On Aug 3, 1:13 pm, Richard <[email protected]> wrote: > Sounds interesting..... but how do you handle write contention to the > memcache datastorage structure from multiple F1's serving client side score > submissions ?
I'm sure it could be done, I have some ideas regarding that (perhaps vary the key structure depending on the instance/user?) but I really don't want to pay the cost of multiple F1s, B1s, etc to test my theory. I might mock up something on my local dev server if I have time over the weekend, but I don't know how memcache works on the local development eclipse plugin. On Aug 3, 1:13 pm, Richard <[email protected]> wrote: > Also, I thought memcache had a size limit ? I store a lot more than just > username + score (including a full stream of all actions the user takes in > the UI to prevent cheating). How much do you store? My general rule of thumb is that I depend on memcache to store 1 GB of data before it starts force-expiring objects (this is for enterprise-level, paid apps). I'm trying to Google around for some documentation regarding the memcache limit, but it seems that there is very little documentation regarding memcache. Frankly, I think shooting for a 100 MB self-imposed-limit should be fine. This is something you really should ask Takashi. -- 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.
