Hey Steve, I see something similar since I've enabled always on. But in my case it seems to be much less extreme. Appstats numbers are more-or-less consistent between the two requests, clearly there is something going on here. The really funny thing is that the CPU ms number is higher than would be caused by a loading request to my app.
This is exactly the same operation, ie fetching the same entity from the datastore (no caching): "Warm" request: Logs: ms=24 cpu_ms=35 api_cpu_ms=8 cpm_usd=0.001236 Appstats: real=11ms cpu=18ms api=8ms overhead=0ms "Cold" request: Logs: ms=110 cpu_ms=2225 api_cpu_ms=8 cpm_usd=0.062068 Appstats: real=93ms cpu=20ms api=8ms overhead=0ms Robert On Sun, May 15, 2011 at 15:51, stevep <prosse...@gmail.com> wrote: > Thanks Brandon, > > I probably mis-communicated. I'm not doing any image manipulation. On- > line handler receives the jpeg bytes posted by client and saves them > in a db.BlobProperty entity property. When the call for the jpeg comes > in, handler simply does a get_by_id, and writes out the > db.BlobProperty value. > > The image call is pretty much exactly like the example at Google's > docs page, but without the query, just the get_by_id: > http://code.google.com/appengine/articles/python/serving_dynamic_images.html > > Did a little testing today, and am pretty sure the cpu variations are > due to my limited volumes. Below are three consecutive image gets. > Notice how only the first one (which came after a period of > inactivity) has the high cpu total. > > I had thought paying to have the on-line handler resident avoided that > startup cpu costs for the first activity after a period of non- > acitivity. Just not groking that I think. So for now a non-issue I > think. My minute volumes are never going to approach using my CPU > daily quote even if every image get averages 13,000ms. If volumes > start to rise, clearly the number of startup cpu instances falls. > > Thanks again, > Steve > > *****Log Extract underscores preceding cpu ms***** > << subsequent calls >> > 2011-05-15 12:36:10.357 /cardimage/80002.jpg 200 201ms_____66cpu_ms > 8api_cpu_ms > 2011-05-15 12:36:04.040 /cardimage/73005.jpg 200 312ms_____63cpu_ms > 8api_cpu_ms > << startup call >> > 2011-05-15 12:35:56.980 /cardimage/74003.jpg 200 204ms_____2427cpu_ms > 8api_cpu_ms > > On May 14, 3:20 pm, "Brandon Wirtz" <drak...@digerat.com> wrote: >> Well Duh, You are generating a JPG, you said "send the bytes" but you are >> modifying, rendering, and compressing a JPG. That takes some CPU. > > -- > 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.
