People always assume that steady traffic yields steady pricing.
If your app spends most of its time waiting on API's like accessing the data store, Small changes in the traffic pattern through out the day can change the amount of concurrency and the number of Instances required to serve the traffic. If you had 1000 people show up for 5 minutes at the same time, your cost will be much more than having 1000 people spread out in order through the day. From: [email protected] [mailto:[email protected]] On Behalf Of Alan Xing Sent: Wednesday, December 14, 2011 12:16 AM To: [email protected] Subject: [google-appengine] 40%+ increase of frontend instance hours over previous day Dear there, Our app 'snsanalytics' experienced more than 40% front end CPU hours usages on Dec 13, comparing to Dec 12. Our traffic level on Dec 13 is actually flat to less comparing to that of Dec 12. Except for the abnormal increase of front end CPU hours, there is no any noticeable change on other resource consumption like db write/read. There is absolutely no change from our side that can explain this increase. We didn't deploy any code in between. We didn't have any heavy lifting operations. Nothing we did is unusual comparing to previous day. Could any one from GAE team help explain/investigate what happened? Thanks, Alan -- 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.
