Congrats! Let's see some graphs afterwards, I'd be interested in seeing how Cloud SQL holds up.
On Aug 3, 2:34 pm, Richard <[email protected]> wrote: > Just moved the scoring over to CloudSQL ..... and got Featured on Google > Play Store 30 min ago. > > Let's PRAY that Cloud SQL saves our ass.... or else I am screwed. > > > > On Friday, August 3, 2012 2:38:32 PM UTC-4, Richard wrote: > > > Sorry, I should have been more explicit. > > > I thought memcache had a size limit on a single object (1MB). Now imagine > > I have 2000 people submitting data for a game. i don't think I will be > > fitting all that into 1MB. Which means I need to store multiple objects > > and fan out/fan in results into memory from memcache (assuming I solve the > > write contention problem... WITHOUT making clients timeout waiting for a > > write lock!). > > > On Friday, August 3, 2012 2:29:20 PM UTC-4, hyperflame wrote: > > >> 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.
