Thanks, Ikai and Robert for shedding some light on this. I agree with you about premature optimization. But now I know how to avoid these hotspots in the first place and since there is a natural opportunity for sharding in my application you've probably saved me a lot of headaches further down the road. Since I'm planning to port an existing app I know for sure that thousand of writes per seconds are a requirement. With tablets beeing as big as 200MB there's really no point in spreading timestamps over a few seconds as I suggested. A couple of hours would probably do.
Wolfram -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/3FJONwpMYXcJ. 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.
