Are you writing lots of indexed data? Indexes are written in parallel; you can easily consume large quantities of CPU in a short time by overindexing. Especially list properties.
Jeff On Wed, Mar 2, 2011 at 2:58 PM, Eloff <dan.el...@gmail.com> wrote: > Hi, > > I have a little driver script for uploading data. It makes a request > to the GAE app, waits for the response, check it, then does it again. > So it's completely serial, and the GAE request finishes completely, no > tasks are started. So how then in less than 2 hours clock-time, I > burned through 41 CPU hours? How is that possible? Just what exactly > is this CPU hour and how is it calculated? > > Baffled, > Dan > > -- > 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.
