That's good to know - if Gardenhose was 10X Spritzer, what I'm trying
to do wouldn't be feasible with Gardenhose because I'd have to buy a
bigger pipe into my "lab". I'd probably run out of patience with CPU
usage in Perl and Ruby, too ;-)
On Feb 28, 8:18 pm, John Kalucki <j...@twitter.com> wrote:
> The gardenhose is very very roughly 3x the default access level (aka
> Spritzer). The algorithm is slightly complicated, and the inputs vary, thus,
> -John Kaluckihttp://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
> On Fri, Feb 26, 2010 at 11:05 PM, M. Edward (Ed) Borasky
> > I don't know anything about "gardenhose", but I do have some data from
> > "sample". Assuming Twitter's published number of 50 million tweets per day
> > is the full firehose (minus spam, according to the blog post), I've
> > estimated that a typical weekday on "sample" is delivering over 3 percent of
> > the total tweet volume.
> > My peak from "sample" this past week was 95,006 tweets for the hour
> > starting "2010-02-24 01:59:59 +0000". The average JSON tweet is about 1400
> > bytes. That peak represents a bit rate of about 300 K bits per second.
> > --
> > M. Edward (Ed) Borasky
> > borasky-research.net/m-edward-ed-borasky/
> > "A mathematician is a device for turning coffee into theorems." ~ Paul
> > Erdos
> > Quoting Mark McBride <mmcbr...@twitter.com>:
> > Hard numbers aren't made public, but it's safe to assume "significantly
> >> more
> >> than spritzer"
> >> ---Mark
> >> On Thu, Feb 25, 2010 at 10:30 AM, rb <rbha...@gmail.com> wrote:
> >> Does anybody knows roughly the gardenhose access to streaming API
> >>> provides what % of total tweets.