Given that the current quota for Channel creation 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 of concurrent users have been reached. What I'm trying to figure out is where is cut-off point should be.
How many concurrent channel connections 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 the Channel API 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's Channel API can handle a large number of concurrent channels. 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 at http://groups.google.com/group/google-appengine?hl=en.
