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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
