Just to be clear, the GAE datastore returns stale results ONLY at a specific time, and only when load is low? Is it because of both of those factors together or just a single one? Seems odd that GAE is reacting slowly just when load is the lowest. Can you post some load graphs?
If the staleness is due to low load, you could always run some fake users to add to the load, then have your backend subtract those fake users when it builds the scoreboards. It wouldn't be hard; you can capture some real users data, save it to a log, then replay it against production servers. On Aug 1, 1:27 pm, Richard <[email protected]> wrote: > Summary so far: > > "Sometimes" (at the same time of day.. when load is lowest), GAE will do a > put() and 5-10 seconds later when I do a query all to create leaderboards > for that game round, I get stale results..... for some of the entries. > This is because the put() has completed, but not the (internal) commit(). -- 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.
