Quoting Ikai "Just be aware of monotonically increasing indexes like timestamps: if you have an application with a high write rate that has a timestamp, this will cause the persistence unit storing the indexes to be unable to be autosplit easily across multiple hardware instances and you will take a performance hit. The solution here is, again, to shard the timestamp by prefixing a value to distribute the writes."
This was in another threat and was left out of the conversation. >From my perspective, this is a huge improvement since most of the times we have to deal timestamps. We handle an application that uses the problematic approach and it's just a bottle neck. We are starting to switch this and notice two things: - it will be nice if the data store implementation can supply the functionality needed to shard it (since seems like a change down deep in the layer). - What would be the best approach to solve this sharding? would unix timestamps would be enough for this? Appreciate your feedback -- http://about.me/david.mora -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
