-- I've seen 15000 mcycle be consumed by a request that took less then two seconds to actually get rendered in my browser.--
I'm importing data into my new app. A single requests puts 500 something entities (one entity group, two db.put() to workaround the 500 entities per single put() limitation). The whole request is usually takes less than 1 second. But the CPU consumption is enourmous: 400,000 mcycles (400 Gigacycles) on average request. As you can see, there is no correlation between CPU usage and timing. BTW, these 400 Gigacycle requests produce warnings that they "used a high amount of CPU were roughly 1.2 times over the average request CPU limit". Just 1.2 times. In another application I get "1.6 times" warnings for requests that consume about 100 times less CPU. Go figure! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
