If you've designed your data model properly writing 2000 entities every 10 seconds probably won't matter much.
+1 to task queues and / or cron. On Friday, July 15, 2011, Raymond C. <windz...@gmail.com> wrote: > If the "2000 players" data can fit into one entity you may use one entity to > store all players' data. Otherwise, I would say what you want to do is not > suitable to be done on AppEngine, which the datastore designed to scale but > not fast and write often. (in your case which is 2000 record updates every 10 > seconds) > There are definitely workarounds and tricks you can employ to workaround all > the AppEngine's limitation. However, if you have not started yet, you should > definitely consider to do it on other platform first because it would be > hundred times easier. Especially you are using Python which the future is > not certain yet on AppEngine. > > > > > > > > > > -- > 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/-/rMAaRbmF6g4J. > 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. > -- ------ Robert Kluin Ezox Systems, LLC -- 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.
