Hey Jamie, Take Stephen's suggestion and see if Pubnub is a better fit for your needs. Just one comment about the concurrent connections: the Channel API uses Google Talk on the backend, connections aren't made directly to your app. They will go through Google's GTalk infrastructure, so you shouldn't hit any concurrency issues (assuming your app is handling requests fast enough that you get new instances spinning up to handle the requests).
Robert On Tue, Apr 12, 2011 at 06:01, Jamie <[email protected]> wrote: > Thanks for all the responses. > > Right now, I'm not re-using channels between clients so I'm > effectively limited to 95K unique hits to my site (which is a lot but > still a limit that *could* be hit easily if my site made TechCrunch, > Mashable, etc.). I will look into channel re-use. > > But my question was more about concurrent channels. I'm unclear on > how GAE implements channels, but I assume having many concurrent > persistent connections open would cause performance issues on the > server, so my question was mainly around how many concurrent channels > could GAE handle? > > On Apr 8, 4:34 pm, "Brandon Wirtz" <[email protected]> wrote: >> What are you doing that you have 95k people a day using your channels? Is >> it porn? You can tell us. >> >> But seriously... Assuming people want to send data to somewhere and not >> have achannelall to themselves you would have to have something like 250k >> users a day, on 24/7. >> >> If you did something "sane" you should be able to spread the load and re-use >> channels as users exit the system. Assuming these users eat, and sleep, and >> leave the house you should be able to accommodate 1m users on the 95k limit. >> And that assumes you use achannelper user, not group the channels based on >> what is going on. >> >> >> >> >> >> >> >> -----Original Message----- >> From: [email protected] >> >> [mailto:[email protected]] On Behalf Of Jamie >> Sent: Thursday, April 07, 2011 11:22 AM >> To: Google App Engine >> Subject: [google-appengine] How manyconcurrentchannels can GAE handle? >> >> Given that the current quota forChannelcreation is 95,040 per day, I'm >> looking into building a degradation path where I would use polling from the >> client side after a certain number ofconcurrentusers have been reached. >> What I'm trying to figure out is where is cut-off point should be. >> >> How manyconcurrentchannelconnections can GAE handle in a performant >> manner? >> >> At a high level, this is how my app works: >> >> 1) Server receives an update from an external source. >> 2) Server notifies each connected client via theChannelAPI about this new >> update. This is currently done in a crude way by looping through all >> clients and sending the msg via ChannelService.sendMessage(). >> >> Given that my site is not very popular right now, it's hard for me to know >> if GAE'sChannelAPI can handle a large number ofconcurrentchannels. >> >> Does anyone have rough numbers or best practices in regards to this? >> >> Thanks, >> J >> >> -- >> 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 >> athttp://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.
