Trolling my logs, I'm coming across cases where there is extreme (~10x) variance in cpu_ms for the exact same code flow, same GET URL and same data (not even any intervening writes to the datastore). I am logging my db.* function accesses, and I have factored out memcache too. For example:
92ms, 142cpu_ms, 74api_cpu_ms, followed by: 965ms, 1500cpu_ms, 74api_cpu_ms Q1: what could cause such a whopping delta? I am using Django, so perhaps template compilation? I used cprofile on the SDK with a similar data/result set, and the first page served was maybe ~2x subsequent pages in total time. Thoughts? Q2: I am assuming the 1st number after the '200' is the wall-clock time-to-server. As the app is single threaded ... how is it able to burn 1500ms less 74ms in only 965ms? Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
