Re: [twitter-dev] Re: the pushing speed for the Twitter's streaming API
You will always receive limit notices if you go beyond the sample. If you get them on a new predicate set, roll-back to the previous predicate set and investigate. If you need more predicates or a higher proportion of tweets, apply for higher access at a...@twitter.com -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sat, Mar 27, 2010 at 11:43 AM, Lawrence wrote: > Do you know the limit though? > > Sometime I upload many tracks, I am afraid my app hits the limit, so I > want to do some detection on my side to make sure there is no tweet > lost., > > Cheers > Lawrence > > On Mar 26, 6:11 pm, Mark McBride wrote: > > They will be discarded. It is very unlikely that any single track term > will > > put you over the limit however. > > > > ---Mark > > > > http://twitter.com/mccv > > > > On Fri, Mar 26, 2010 at 4:17 PM, Lawrence wrote: > > > Hi Mark, > > > Thank you for your reply, but could you explain more? For example, if > > > I search a very hot key word (not a, or o ), and the tweet flow is > > > 5000 tweets/min. Does this mean that I only be able to receive > > > 2000tweets/min because the restriction? what about the other 3000 > > > tweets? Will they be delayed or just discarded? > > > > > Cheers > > > Lawrence > > > > > On Mar 26, 3:57 pm, Mark McBride wrote: > > > > You are probably getting limit messages when searching for those > terms. > > > The > > > > filter endpoints will return all tweets up to a predefined percentage > of > > > the > > > > total tweet stream. > > > > > > ---Mark > > > > > >http://twitter.com/mccv > > > > > > On Fri, Mar 26, 2010 at 3:49 PM, Lawrence > wrote: > > > > > HI Everyone, > > > > > I am wondering if there is a rate limiting for the pushing speed > for > > > > > the Twitter's streaming API? > > > > > > > I first use the Twitter searching API to search "a" and it returns > > > > > 2300 tweets per min to me. And then I tested "o", it also returned > me > > > > > around 2400 tweets per min. Now, I tested "track = a, b". > > > > > Theoretically, the streaming API should returns me more than 4000 > > > > > tweets per min. However, I found the streaming API still only > returns > > > > > me about 2400 tweets! > > > > > > > My downloading speed is 16.68Mb/s So it seems that I still have > enough > > > > > spare bandwidth, but the Twitter just does not push more data to > me. > > > > > Is this true? Are there any internal limitation has been done by > > > > > Twitter? > > > > > > > Cheers > > > > > Lawrence > > > > > > > To unsubscribe from this group, send email to > twitter-development-talk+ > > > > > unsubscribegooglegroups.com or reply to this email with the words > > > "REMOVE > > > > > ME" as the subject. > > > > > To unsubscribe from this group, send email to twitter-development-talk+ > > > unsubscribegooglegroups.com or reply to this email with the words > "REMOVE > > > ME" as the subject. > > To unsubscribe from this group, send email to twitter-development-talk+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Re: the pushing speed for the Twitter's streaming API
Do you know the limit though? Sometime I upload many tracks, I am afraid my app hits the limit, so I want to do some detection on my side to make sure there is no tweet lost., Cheers Lawrence On Mar 26, 6:11 pm, Mark McBride wrote: > They will be discarded. It is very unlikely that any single track term will > put you over the limit however. > > ---Mark > > http://twitter.com/mccv > > On Fri, Mar 26, 2010 at 4:17 PM, Lawrence wrote: > > Hi Mark, > > Thank you for your reply, but could you explain more? For example, if > > I search a very hot key word (not a, or o ), and the tweet flow is > > 5000 tweets/min. Does this mean that I only be able to receive > > 2000tweets/min because the restriction? what about the other 3000 > > tweets? Will they be delayed or just discarded? > > > Cheers > > Lawrence > > > On Mar 26, 3:57 pm, Mark McBride wrote: > > > You are probably getting limit messages when searching for those terms. > > The > > > filter endpoints will return all tweets up to a predefined percentage of > > the > > > total tweet stream. > > > > ---Mark > > > >http://twitter.com/mccv > > > > On Fri, Mar 26, 2010 at 3:49 PM, Lawrence wrote: > > > > HI Everyone, > > > > I am wondering if there is a rate limiting for the pushing speed for > > > > the Twitter's streaming API? > > > > > I first use the Twitter searching API to search "a" and it returns > > > > 2300 tweets per min to me. And then I tested "o", it also returned me > > > > around 2400 tweets per min. Now, I tested "track = a, b". > > > > Theoretically, the streaming API should returns me more than 4000 > > > > tweets per min. However, I found the streaming API still only returns > > > > me about 2400 tweets! > > > > > My downloading speed is 16.68Mb/s So it seems that I still have enough > > > > spare bandwidth, but the Twitter just does not push more data to me. > > > > Is this true? Are there any internal limitation has been done by > > > > Twitter? > > > > > Cheers > > > > Lawrence > > > > > To unsubscribe from this group, send email to twitter-development-talk+ > > > > unsubscribegooglegroups.com or reply to this email with the words > > "REMOVE > > > > ME" as the subject. > > > To unsubscribe from this group, send email to twitter-development-talk+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
Re: [twitter-dev] Re: the pushing speed for the Twitter's streaming API
They will be discarded. It is very unlikely that any single track term will put you over the limit however. ---Mark http://twitter.com/mccv On Fri, Mar 26, 2010 at 4:17 PM, Lawrence wrote: > Hi Mark, > Thank you for your reply, but could you explain more? For example, if > I search a very hot key word (not a, or o ), and the tweet flow is > 5000 tweets/min. Does this mean that I only be able to receive > 2000tweets/min because the restriction? what about the other 3000 > tweets? Will they be delayed or just discarded? > > > Cheers > Lawrence > > > > On Mar 26, 3:57 pm, Mark McBride wrote: > > You are probably getting limit messages when searching for those terms. > The > > filter endpoints will return all tweets up to a predefined percentage of > the > > total tweet stream. > > > > ---Mark > > > > http://twitter.com/mccv > > > > On Fri, Mar 26, 2010 at 3:49 PM, Lawrence wrote: > > > HI Everyone, > > > I am wondering if there is a rate limiting for the pushing speed for > > > the Twitter's streaming API? > > > > > I first use the Twitter searching API to search "a" and it returns > > > 2300 tweets per min to me. And then I tested "o", it also returned me > > > around 2400 tweets per min. Now, I tested "track = a, b". > > > Theoretically, the streaming API should returns me more than 4000 > > > tweets per min. However, I found the streaming API still only returns > > > me about 2400 tweets! > > > > > My downloading speed is 16.68Mb/s So it seems that I still have enough > > > spare bandwidth, but the Twitter just does not push more data to me. > > > Is this true? Are there any internal limitation has been done by > > > Twitter? > > > > > Cheers > > > Lawrence > > > > > To unsubscribe from this group, send email to twitter-development-talk+ > > > unsubscribegooglegroups.com or reply to this email with the words > "REMOVE > > > ME" as the subject. > > To unsubscribe from this group, send email to twitter-development-talk+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Re: the pushing speed for the Twitter's streaming API
Hi Mark, Thank you for your reply, but could you explain more? For example, if I search a very hot key word (not a, or o ), and the tweet flow is 5000 tweets/min. Does this mean that I only be able to receive 2000tweets/min because the restriction? what about the other 3000 tweets? Will they be delayed or just discarded? Cheers Lawrence On Mar 26, 3:57 pm, Mark McBride wrote: > You are probably getting limit messages when searching for those terms. The > filter endpoints will return all tweets up to a predefined percentage of the > total tweet stream. > > ---Mark > > http://twitter.com/mccv > > On Fri, Mar 26, 2010 at 3:49 PM, Lawrence wrote: > > HI Everyone, > > I am wondering if there is a rate limiting for the pushing speed for > > the Twitter's streaming API? > > > I first use the Twitter searching API to search "a" and it returns > > 2300 tweets per min to me. And then I tested "o", it also returned me > > around 2400 tweets per min. Now, I tested "track = a, b". > > Theoretically, the streaming API should returns me more than 4000 > > tweets per min. However, I found the streaming API still only returns > > me about 2400 tweets! > > > My downloading speed is 16.68Mb/s So it seems that I still have enough > > spare bandwidth, but the Twitter just does not push more data to me. > > Is this true? Are there any internal limitation has been done by > > Twitter? > > > Cheers > > Lawrence > > > To unsubscribe from this group, send email to twitter-development-talk+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.