Assuming that a channel setup costs 2.77 seconds, having just 10,000 active users setup 4 channels per day would cost $92.30 per month. That's not counting any CPU costs for actually sending messages.
At that rate, I can't really use the channel API as much as I'd like and I have to look at alternatives such as Beacon now that I know how cool this technology is. Here's to hoping that the GAE team can bring down the cost of setting up a channel by at least a factor of 10. - Andy Kim On Dec 10, 2010, at 7:53 PM, Tom Wu wrote: > Hi Andy, > > Here is 2770ms. Compare to using the beaconn + urllib, the channel api really > cost a lot. > > <1E3.gif> <1E3.gif> > Tom Wu > > > 2010/12/11 Andy Kim <[email protected]> > The new Channel API is awesome and it opens up many possibilities on what I > can do with GAE. I have noticed however, that creating a channel takes about > 2800 ms of API CPU time. Is everyone else seeing similar times or am I doing > something wrong here? > > -- > 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. -- 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.
