You might try to submit a billing issue asking for a credit or something: http://code.google.com/support/bin/request.py?contact_type=AppEngineBillingSupport
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 On Mon, Aug 8, 2011 at 14:53, observer247 <[email protected]> wrote: > I would like to know clearly if the over-usage charges are: > > expected for the kind of usage I have and the code we have ? or > a bug caused by some bug or issue with app engine. > > Based on that, we will make a decision. Because a simple memcache read > and return was using high cpu numbers. We need that answer to decide > whether to: > > optimize the code ? or > wait for Google to fix issues on their side ? or > not wait for an infinite time before we can get an answer while paying > $600 a month and move to another host ? > > As days are flying (15 days gone by already), I am almost decided that > it was a bad idea to assume that it was ok to host my application on a > proprietary network hosted by a reliable company. Now I guess we > should spend the next 15 days trying to rewrite the code in php/mysql > and move to a more portable host. > > We are still waiting for the answer. > > > On Aug 3, 1:27 am, Johan Euphrosine <[email protected]> wrote: >> Sorry for the late followup, I just updated your issue. >> >> 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#a... >> >> 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-... >> >> 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. >> >> >> >> >> >> >> >> >> >> On Wed, Aug 3, 2011 at 4:18 AM,observer247<[email protected]> wrote: >> > Issue number is 5415 >> >> > It has been more than a week and I am yet to get a useful response on >> > the ticket. >> >> > On Jul 21, 4:20 am, Johan Euphrosine <[email protected]> wrote: >> >> >> 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=Produc... >> >> >> If you do so, please reply to this thread with the issue number, so we >> >> can followup. >> >> >> Hope that helps. >> >> >> On Thu, Jul 21, 2011 at 10:24 AM,observer247<[email protected]> wrote: >> >> > Is this is because of the new pricing, I would rather move out of >> >> > Google app engine. >> >> >> > We have over 10 apps serving our iPhone apps. It will take us a lot of >> >> > effort to port this code to php/mysql but I guess if the pricing >> >> > changes like this, we cannot afford to pay such high prices. >> >> >> > I am not sure if there is a phone number or support chat. When I am >> >> > paying $1000 per month for a service, I would expect to talk to a real >> >> > person and share with him the issues I am facing. >> >> >> > On Jul 20, 1:14 am,observer247<[email protected]> wrote: >> >> >> Almost the same usage is now triggering 10times the daily cost ! Not >> >> >> sure what changed as far as billing. >> >> >> >> Checking appstats and instances. >> >> >> >> On Jul 19, 2:55 pm, Barry Hunter <[email protected]> wrote: >> >> >> >> > Have you tried >> >> >> > AppStats?http://code.google.com/appengine/docs/python/tools/appstats.html >> >> >> >> > On Tue, Jul 19, 2011 at 8:31 PM,observer247<[email protected]> wrote: >> >> >> > > My python app engine app is somewhat popular, mainly used as via >> >> >> > > api >> >> >> > > from my iphone app. >> >> >> >> > > Recently I am seeing high over usage charges. >> >> >> >> > > The most used call already use 15 CPU hours , with stats: >> >> >> > > 3.7 calls/sec 26.15K requests in 12hrs 603 (0) >> >> >> > > [cpu] >> >> >> >> > > HTTP/1.1" 200 1839 - "QandA/5.4 CFNetwork/485.12.7 Darwin/10.4.0" >> >> >> > > "may.latest.nuvusanswers.appspot.com" ms=1490 cpu_ms=467 >> >> >> > > api_cpu_ms=0 >> >> >> > > cpm_usd=0.013200 pending_ms=1058 throttle_code=1 >> >> >> > > instance=00c61b117c8b0de1286e8d90c22f4d5b3897c8 >> >> >> >> > > This call just reads a memcache and returns the data. Thats it. >> >> >> > > Will >> >> >> > > really like to know are memcache reads so expensive ? Am I using a >> >> >> > > lot >> >> >> > > more memcache that I need ? >> >> >> >> > > I have removed all other versions and have just one version >> >> >> > > running. >> >> >> > > The number of instances now is >> >> >> >> > > 28 total 0.510 (Average QPS) 281.1 ms (Average Latency) >> >> >> > > 59.5 MBytes >> >> >> > > (Average Memory) >> >> >> >> > > As this is the most expensive call, I am first going after that. >> >> >> > > but I >> >> >> > > am seeing most of my calls are now using a LOT of CPU. Will be >> >> >> > > great >> >> >> > > if anyone can point me to things I can debug to find out the high >> >> >> > > usage across the board. >> >> >> >> > > Thank you for reading this ! >> >> >> >> > > -- >> >> >> > > 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 >> >> >> > > athttp://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 [email protected]. >> >> > To unsubscribe from this group, send email to >> >> > [email protected]. >> >> > For more options, visit this group >> >> > athttp://groups.google.com/group/google-appengine?hl=en. >> >> >> -- >> >> Johan Euphrosine (proppy) >> >> Developer Programs Engineer >> >> Google Developer Relations >> >> > -- >> > 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 >> > athttp://groups.google.com/group/google-appengine?hl=en. >> >> -- >> Johan Euphrosine (proppy) >> Developer Programs Engineer >> Google Developer Relations > > -- > 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. > > -- 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.
