The bigger your app the Better the savings. Some of the small apps that average 3 f1's cost a LOT more on f2's because the scheduler would spike to 4 instances when it only needed them briefly and over compensating suddenly cost twice as much. (Lot is a % increase not a $ increase)
If you are running Python 2.7 and have 10 instances normally the advantage of F4's is HUGE. We were blown away. The Larger Ram, and the faster handling resulted in SAVING 30% by running bigger instances. I'm not sure that Google could build a tool that would deal with this at both ends of the spectrum. From: [email protected] [mailto:[email protected]] On Behalf Of Adam Sah Sent: Wednesday, January 04, 2012 3:37 PM To: [email protected] Subject: [google-appengine] Re: First impressions of F1 Through 4 oops, forgot to mention. Googlers-- if you're reading this, a supercool, googley feature: analyze the app's traffic and predict the $-impact of settings changes to idle instance and pending latency. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/CT5YtjItjGgJ. 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.
