Hmm... On a second thought, the put operation is perhaps also costly in terms of CPU time. I haven't tried doing 20 puts in one page access. Maybe that would also consume a lot of CPU time. On a practical level, this is usually not a big problem when the traffic to the application is low, but imagine an application like Twitter being implemented using GAE and with that kind of huge traffic Twitter has. Millions of datastore updates every minute. If an application like that would run on GAE, the Quota costs for CPU time alone would become astronomical!
P.S. Twitter is actually using the Amazon Elastic Compute Cloud at the moment I think. ;-) On Jun 24, 6:36 pm, Anders <i...@blabline.com> wrote: > Sometimes delete operations are implemented to be allowed to take more > time than put operations. Could it be that the delete operation in GAE > has been allowed to be slow in order to make put operations and/or > queries faster? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
