It has been a few days now and I'm still experiencing much higher api cpu usage when aadding entities to the datastore than I did before the 1.2.5 release. So I assume this is not just an accounting error by Google and I’m at a loss to know what to do.
I would really appreciate if someone at Google could comment or suggest possible reasons why the reported api_cpu_ms values could have significantly increased for a request handler code that hasn’t changed and when my data models and indexes haven’t changed either? Really appreciate any help On Sep 4, 9:52 pm, herbie <4whi...@o2.co.uk> wrote: > Thanks for our reply. I hope it is an accounting error on Google's > side. Can anyone at Google comment? > > I'm still getting logs reporting api_cpu_ms values x3 than they were > before. (The response time for the request is still 'quick' - aprox > 800ms as before). So I still have no idea why the api_cpu_ms is so > high now. > > On Sep 4, 5:24 pm, bFlood <bflood...@gmail.com> wrote: > > > I have seen a very large increase in CPU time with no changes as well, > > so much so that I figured it was just an accounting error on Google's > > side > > > brian > > > On Sep 4, 11:59 am, herbie <4whi...@o2.co.uk> wrote: > > > > Could the new SDK release caused this? > > > > On Sep 4, 10:26 am, herbie <4whi...@o2.co.uk> wrote: > > > > > Have there been any recent changes to the DataStore or API (I’m using > > > > python) that can account from a dramatic increase in api cpu usage > > > > when putting entities into the datastore? > > > > > My app has a request handler that creates about 100 new entities in > > > > the datastore from data posted by the user. > > > > > A few weeks ago the average api_cpu_ms for a single request to this > > > > handler was aprox 7000 api_cpu_ms (expensive enough!) > > > > > But I tested it again last night and now its about 22000 api_cpu_ms - > > > > a 3x increase!! > > > > > The request handler hasn’t changed and the entity models haven’t > > > > changed, my indexes haven’t changed and user data in the post hasn’t > > > > changed. So I can not account for the huge increase in api_cpu_ms. > > > > > (I’ve run older versions of my app and still the api_cpu_ms is about > > > > 22000. Again it used to be about 7000) > > > > > FYI. One request creates about 100 new entities, all in a single > > > > entity group, using a batch put() in a transaction. The entities > > > > have 10 properties, but only 5 are indexed (no list properties) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
