So this is what we did: 24 hours back we changed the code to:
class GetUserAudio(webapp.RequestHandler): def get(self): self.response.out.write("0") return We just return after writing 0. /getAvatar 1.3 40.63K 600 (0) 9% CPU Time $0.10/ CPU hour 46% 46% 122.93 of 268.50 CPU hours $11.65 So we are paying around $1 per day for a call which just returns and does almost nothing. It takes 600 cpu_ms for this call ? 2011-08-11 22:28:30.125 /getUserAudio?userid=11445171&hasaudio=1 200 315ms 676cpu_ms 0kb ndA/5.4 CFNetwork/485.13.9 Darwin/11.0.0 166.205.10.107 - - [11/Aug/2011:22:28:30 -0700] "GET /getUserAudio? userid=11445171&hasaudio=1 HTTP/1.1" 200 125 - "ndA/5.4 CFNetwork/ 485.13.9 Darwin/11.0.0" "may.latest.nuvusanswers.appspot.com" ms=315 cpu_ms=677 api_cpu_ms=0 cpm_usd=0.018842 instance=00c61b117c3aa282423e18cdf09af851cead373f If we are charged at 600 cpu_ms for a return 0 function, there is definitely something wrong here. This has started happening around a month back. Every day we are paying $20 for these issues. Worst part is we still did not get an answer about if this is legitimate or a bug in billing. Please confirm why. On Aug 11, 4:16 pm, Johan Euphrosine <pro...@google.com> wrote: > Hi, > > 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. > > > > > > > > On Thu, Aug 11, 2011 at 8:27 PM,observer247<prem...@gmail.com> wrote: > > Is there a phone number I can call. > > > We have discovered something weird here. I think these billing > > details are flawed ! Seriously did not expect this from Google. I am > > waiting for a genuine response for almost a month and you continue > > billing us. > > > And now this experiment from us tells me that there must be something > > weird that happened in your system that your CPU calculations are > > messed up and keeps billing us even for : > > > "return 0" statements. > > > 600 Avg CPU for just a single "return 0". > > > I value my money but I am stuck with app engine till we can port our > > code somewhere else. > > > On Aug 9, 12:43 am, Johan Euphrosine <pro...@google.com> wrote: > >> Hi, > > >> 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, > > >> On Mon, Aug 8, 2011 at 10:07 PM, David <wordsmithg...@gmail.com> wrote: > >> > I've been down that road trying to get Google to fix their issues for > >> > a good year. Almost all of my production issues filed have gone > >> > unanswered. The ones that did were about a month later. I've come to > >> > realize app engine is only good to get something up quickly or if you > >> > don't care about service availability or support and you don't mind > >> > not having any control when something behind the server API goes > >> > wrong. Not to mention every time they push out new versions, things > >> > break for up to a week before they start to look stable again. I've > >> > already started porting my app to work on an environment I have more > >> > control over when things go wrong. I'd suggest the same for anyone > >> > that has constant issues like I have. > > >> > Good luck. > > >> > David > > >> > On Aug 8, 11:53 am,observer247<prem...@gmail.com> 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 <pro...@google.com> 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<prem...@gmail.com> 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 <pro...@google.com> 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<prem...@gmail.com> > >> >> > >> 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<prem...@gmail.com> 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 <barrybhun...@gmail.com> 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<prem...@gmail.com> 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 > >> >> > >> >> > > google-appengine@googlegroups.com. > >> >> > >> >> > > To unsubscribe from this group, send email to > >> >> > >> >> > > google-appengine+unsubscr...@googlegroups.com. > >> >> > >> >> > > 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 > >> >> > >> > google-appengine@googlegroups.com. > >> >> > >> > To unsubscribe from this group, send email to > >> >> > >> > google-appengine+unsubscr...@googlegroups.com. > >> >> > >> > 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 > >> >> > > google-appengine@googlegroups.com. > >> >> > > To unsubscribe from this group, send email to > >> >> > > google-appengine+unsubscr...@googlegroups.com. > >> >> > > 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 google-appengine@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > google-appengine+unsubscr...@googlegroups.com. > >> > For more options, visit this group > >> > athttp://groups.google.com/group/google-appengine?hl=en. > > >> -- > >> Johan Euphrosine (proppy) > >> Developer > > ... > > read more » -- 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.