Gardenhose is around what... 1.5M tweets/day? I think that's about right. Yes, that is a LOT of data and going through it then takes a lot. My server started crying a bit when I switched up to gardenhose. I'm going to have to get a bigger one if I ever can consume the firehose
On Jun 11, 5:04 pm, "M. Edward (Ed) Borasky" <[email protected]> wrote: > I clocked spritzer (JSON feed) at something like 29,000 tweets per > hour between 10 and 11 AM PDT the other day. That may in fact be more > data than I can practically use. > > On May 25, 11:12 pm, John Kalucki <[email protected]> wrote: > > > The sampling rates of the Streaming API and the REST API public > > methods are independent, and any similarity in proportions is > > basically happenstance. > > > Currently, Gardenhose will average three timesSpritzer, with some > > deviation. The rate of all statuses varies significantly throughout > > the day and week, so be sure you are comparing the exact same time > > periods. > > > -John Kalucki > > Services, Twitter Inc. > > > On May 25, 7:20 pm, Twittledee <[email protected]> wrote: > > > > Hello: > > > In an answer to a different question in this group, Doug said that > > > thespritzerwas supposed to be as fast as the datamining feed. Is > > > that right? We only get 5.3 msg/sec on avg. for thespritzer. If this > > > is right, then we are only getting half the speed we should be ... and > > > I will have to debug our code. We get 18.7 msg/sec avg. on the > > > gardenhose, so I thought everything was right/okay. Can others state > > > their rates for these two streams? > > > > Thanks
