GAE is optimized for datastore read operations. No problem in scaling for get operations.
The put scaling depends on if you are updating a particular entity group more then 1 or 2 times a second. If not then there is no problem in scaling put operations. If updating one (1) entity group more then 1/sec but it happens in bursts you can use the task queue to perform the update, it will retry in case you have a transaction exception. 2011/2/10 Atif Gulzar <atif.gul...@gmail.com>: > Hi, > I am estimating whether AppEngine is scalable for ~200 get/sec and about 50 > put/sec RPC calls. > I have ran the AppStat on my current app, which have currently very low > traffic about ~20get and ~4put/sec. And the average time for my get rpc > calls is about ~10ms while ~100ms for the put calls. > Actually, I have a handler which calls a model on each call to get the user > data. And I am expecting the load on this handler for about ~200hits/sec > And some of these users may update some data. And I am expecting about > ~50hits/sec on this update handler. > I am just looking whether appengine will be scaleable for my above > requirements? > Thanks > > > -- > Best Regards, > Atif Gulzar > > I ◘◘◘◘ Unicode, ɹɐzlnƃ ɟıʇɐ > > -- > 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. > -- 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.
