> ms=1490 cpu_ms=467 api_cpu_ms=0
> cpm_usd=0.013200 throttle_code=1
The pending ms value (1058) is the time the request was waiting to be
serviced by an instance; as I recollect it gets added to the request
latency (the ms value). As a note, that request does not seem to make
any API calls. I don't recall what throttle_code 1 means, would be
great if these were documented somewhere
(http://code.google.com/p/googleappengine/issues/detail?id=4405),
Robert
> --
> 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-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>
Is this issue resolved now ? What is your application id ?
Feel free to open a Production Issue if this is directly affecting
your application operation:
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
--
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations
Feel free to open a Production Issue for problem like this affecting
directly your application operation:
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
If you do so, please reply to this thread with the issue number, so we
can followup.
Hope that helps.
About 1:1 support, we are currently rolling a Trusted Testers Program
for Paid support, feel free to contact me directly if you are
interested.
Hope that helps.
On Thu, Jul 21, 2011 at 10:24 AM, observer247 <pre...@gmail.com> wrote:
FYI, we believe that the problems experienced by most of the Apps on
this thread were due to a temporary datastore latency, as you can see
there:
http://code.google.com/status/appengine/detail/datastore/2011/07/27#ae-trust-detail-datastore-get-latency
This cascaded into a higher HTTP latencies for some Python
applications running on Master/Slave Datastore Replication system:
http://code.google.com/status/appengine/detail/serving/2011/07/27#ae-trust-detail-helloworld-get-latency
We offered the affected app to assist them to migrate to HRD, where
apps are not subject to those transient latency issues.
For the record Issue #5415 might be a different beast, as appstats
doesn't report any datastore operation but still high latency.
I already escalated it to the engineering team and will followup on
the bug report once I have any updates.
Hope that helps.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
I'd have documentation ready to demonstrate that the app is
experiencing abnormal latency leading to higher charges. Have you
tried profiling with AppStats? One thing I find very odd about your
log entry is that you're seeing 0 api cpu ms, yet you're making a
memcache call. Is that the case with all of your high-cpu requests?
Is it the case with all of your "normal" requests?
Robert
Your issue has already been escalated internally on July 28 2011 but
single application failure usually take more time to get diagnosed
than problems affecting more than one application.
I just updated the production ticket with more detail on the ongoing
investigation.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
FYI, stats I computed for the weekly community update shows that since
3 weeks, all productions issues have been escalated in less than 48
hours, so hopefully this is getting better.
Also as part of the new pricing model going out later this year, we
will provide SLA and Paid support, see the following page for more
details:
http://www.google.com/enterprise/cloud/appengine/pricing.html
Regards,
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
There is no phone support for AppEngine ATM, as I mentioned before we
will offer SLA and Paid support as part of the new pricing model later
this year.
Please followup on the Production ticket you opened:
http://code.google.com/p/googleappengine/issues/detail?id=5415
If you could provide a test url for the CPU spikes you reproduce
there, that would help use to put a better diagnostic on the issue.
Thanks in advance.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.