I know, I'm going to hit the write limit with a timestamp I need to update 
on every write and which needs to be indexed.

As an alternative to sharding: What do you think about adding time jitter 
to the timestamp, that is, changing time randomly by a couple seconds? In 
my application the timestamp being off by a couple senconds wouldn't pose a 
problem.

Now what I need to know is: How many index entries can I expect to go into 
one tablet? This is needed to estimate the amount of jitter necessary to 
avoid hitting the same tablet on every write.

Any insights on this?

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/-/r0SVTq6i4iEJ.
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.

Reply via email to