I disagree with your assessment that 0.01 CPU is unrealistic. Here's an example.
User sends a request for a page.. cold start, need new instance ~ 10,000 ms = 10s. User stares at it for 2 seconds, clicks an interaction... we're unlucky, new instance ~10,000 ms = 10s. User executes a task that delegates something to the queue. Oh no, start of a task, new instance ~10,000 ms = 10s. And that's where 30s of computation went. In low usage apps this happens all the time. I'm gonna write out the math again since I don't trust my numbers: 60 seconds * 60 minutes * 24 hours = 86,400. *If* (this is not a valid assumption, but worst case scenario) 10,000 users were evenly distributed over the 24 hours, there will be 8 seconds between each user visit, enough time for the above 30s usage scenario to take place repetitively. Even making more realistic assumptions, I would argue that there is still a quite likely chance that each user could use 36s, or 0.01 CPU hours in a twitter / facebook / user intensive application. Funny, but it could be the case that there is a threshold of user numbers that once reached drastically reduces your costs due to instances being alive the whole time. On Jun 22, 7:52 pm, "Ikai L (Google)" <[email protected]> wrote: > The broken number in that thread is 0.01 CPU hours per user per day. You do > realize that is 36 seconds of computation time per User, right? If we were > to be aggressive and assume 3.6 seconds instead, it brings those off the > cuff costs of 100,000 users (who are obviously very heavily engaged, as they > are returning every day and consuming 3.6s of CPU time) to $300. Not bad. > But the real numbers are probably lower. > > On Tue, Jun 22, 2010 at 5:37 PM, Tristan <[email protected]>wrote: > > > > > > > Yeah... looking at it again I can't even tell you where I got the > > numbers, it looks like I just made them up... > > > Here's the thread with the corrected numbers (why did this thread get > > hijacked?) > > >http://groups.google.com/group/google-appengine/browse_thread/thread/... > > > On Jun 22, 7:35 pm, "Ikai L (Google)" <[email protected]> wrote: > > > It's highly unlikely 10,000 users would cost that much money. There are > > > extremely large customers paying a fraction of that. > > > > Here's a recent blog post from the developer of the Humble Indie Bundle: > > > >http://googleappengine.blogspot.com/2010/06/how-app-engine-served-hum... > > > > 1 million uniques for $71 USD. Granted, the usage pattern isn't the same > > as > > > Twitter, where each user may send out 100 tweets a day (who does this? I > > am > > > a pretty heavy tweeter and I don't come close to this), but even that > > > traffic profile shouldn't come anywhere near $24k. > > > > On Tue, Jun 22, 2010 at 4:47 PM, Jaroslav Záruba > > > <[email protected]>wrote: > > > > > I'm curious too. Also I'd love to read the post you mentioned. Pretty > > > > please! > > > > > On Wed, Jun 23, 2010 at 1:44 AM, Martin Webb <[email protected] > > >wrote: > > > > >> I want to find out what typical costs are being paid for running apps > > on > > > >> app engine say per 10,000 for 100,000 users. I read a post today that > > gave > > > >> an example - and it was an example where it concluded that 10,000 > > users > > > >> would cost $24000 a month - which is crazy - i cant imagine one can > > make $2 > > > >> per user from advertising. > > > >> Can anyone shed any light on what the typical costs might be. > > Obviously it > > > >> depends on the app/storage - but i'm talking about typical examples. > > lets > > > >> say to run an app like twitter per 10,000 users. > > > >> Any help much appreciated. > > > > >> Regards > > > > >> *Martin Webb* > > > > >> -- > > > >> 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]<google-appengine%2Bunsubscrib > > > >> [email protected]><google-appengine%2Bunsubscrib > > [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]<google-appengine%2Bunsubscrib > > > > [email protected]><google-appengine%2Bunsubscrib > > [email protected]> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-appengine?hl=en. > > > > -- > > > Ikai Lan > > > Developer Programs Engineer, Google App Engine > > > Blog:http://googleappengine.blogspot.com > > > Twitter:http://twitter.com/app_engine > > > Reddit:http://www.reddit.com/r/appengine > > > -- > > 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]<google-appengine%2Bunsubscrib > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog:http://googleappengine.blogspot.com > Twitter:http://twitter.com/app_engine > Reddit:http://www.reddit.com/r/appengine -- 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.
