This isn't how Site Streams should work. First, you should only open 25 connections per second. Second, have you calculated how much bandwidth is required to download all of the initial notifications and subsequent updates? I'd suspect insufficient bandwidth as the first cause of these kinds of symptoms.
-John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Sun, Nov 14, 2010 at 12:13 PM, N <n...@h7a.org> wrote: > When my program makes hundreds of connections with Site Stream to > observe tens of thousands of users, the latency for every status > messages seems to start off like 10~30 minutes. It gradually gets > better and will be like 0~1 seconds within an hour or two, though. > > Is this expected behavior? > > Because this wouldn't be the case when it'd make much much fewer > connections, I'm guessing something must be wrong somewhere. The > traffic isn't any issue and my program can handle much more data > simultaneously. > > It appears to me that Site Stream server is taking too much time to > send out many "friend list" to clients. > > Any thoughts? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
