If you do hit it, it can get quite complicated. It is also a royal PITA to figure out that is what's happening. The basic idea will be to somehow "shard" the index, so that writes aren't all going to the "end" of the index. How you do that can be quite app dependent.
Robert On Tue, Jan 31, 2012 at 16:11, Jeff Schnitzer <[email protected]> wrote: > On Tue, Jan 31, 2012 at 10:07 AM, Richard Watson > <[email protected]> wrote: >> Jeff wrote: >>> 2) Throughput limit on tablet splits for increasing index values >> >> How do you avoid timestamps if you would otherwise use them, for example >> needing to query by the time something occurred? I know Itai put a couple >> tips into his post, just asking how others have solved it. > > Wild guess: There are very few people who hit this write rate limit > so nobody really thinks about it. Even Ikai's advice is to ignore it > until it becomes a problem, because for 99.9% of apps it never will > be. > > Jeff > > -- > 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.
