Cayden, I'm a big fan of Python 2.7, but I wouldn't dream of telling someone running this large of an App to move to it right now. I've seen what happens when the scheduler gets things wrong, and that "increased latency" results in "massive time outs".
Python 2.7 is awesome if all of your requests are under 7 seconds. But our experience has been that if you have more than 1 in 50 requests taking more than 7 seconds python 2.7 will buckle under load. I blame the scheduler, and that might not be the problem, but I know that when you start having Long requests things start timing out, and it appears to be that the scheduler is willing to stack things poorly, under load these timeouts cascade. -Brandon -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Cayden Meyer Sent: Monday, January 02, 2012 7:10 PM To: Google App Engine Subject: [google-appengine] Re: Where to start optimizing cost? Hi Andrin, The admin console can provide a great deal of information on where your costs are coming from. I know that you specified that you wanted ways to monitor rather than solutions to reduce costs, however these are four fairly easy to measure changes: - If your application is not CPU bound you may wish to migrate to Python2.7. This can lower the number of instances required to serve the same amount of traffic. Changes can be seen by comparing the number of active instances with python2.7 to serve traffic y vs activate instances with python2.5 to serve traffic y. Note: Python 2.7 is currently experimental and the your latency may increase when moving to Python2.7. - Using memcache can reduce datastore operations. - Use edge caching where possible, this can reduce the number of instances required to serve traffic. - If you can roughly predict the amount of traffic you will receive, discount instance hours are a good way to reduce costs. Hope this helps you optimize your application. There are more ways to optimize your application, however these are just a few simple ones which can make a quite a difference. Cayden MeyerProduct Manager, Google App Engine On Jan 1, 2:42 am, Andrin von Rechenberg <[email protected]> wrote: > Hey there > > I'm an absolute GAE-Lover! The only thing that is bothering me is cost. > We spend about $10'000 a month in GAE cost. That's just too much for > the traffic we serve. We are starting to look around for alternatives, > but I'd really love to stay with GAE and just optimize the system. > > One of GAE's biggest flaws IMHO is that it is really hard to see where > the costs are coming from. (Yes we have appstats in place, but our > system is just too big to manually sample hundreds of requests). > > So here is a feature request that might help us optimize and stay with GAE: > *Show cost per URI in the dashboard. That would be incredibly > helpful.* > > Does anyone know of an existing elegant way to figure out where the > cost come from? (I'm looking more for a way to measure rather than > software solutions like "use memcache"). I could do something with > prodeagle.com and estimate the cost per request myself but I'd rather > use an already existing solution... > > Cheers, > -Andrin -- 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.
