How Ravelry Scales to 10 Million Requests Using Rails

Re:How Ravelry Scales to 10 Million Requests Using Rails by sophacles on Wednesday September 23, 2009 @10:17AM (#839277)

I strongly suspect a flaw in your statistics: I'm willing to put money on this site having a spikey workload, not a constant workload. There are probably hours in a row that 6 of those servers sit idle.

Rant: I wish technical sites would stop using req/day as a metric. It leads to the op type of analysis. At the very least, such articles could use a format of "X req/day peaking at Y/s". Maybe if the NYT was writing it would be ok to use req/day but a sight who's tagline is: "High Scalability Building bigger, faster, more reliable websites." should know better.

[ Parent | on HN ]

Re:How Ravelry Scales to 10 Million Requests Using Rails by warfangle on Wednesday September 23, 2009 @11:23AM (#839408)

Rebuttal accepted, observed, and original post withdrawn.

[ Parent | on HN ]

Re:How Ravelry Scales to 10 Million Requests Using Rails by toddh on Wednesday September 23, 2009 @12:12PM (#839523)

What should I use in a title that is informative and gets people interested enough to read an article? A munin graph isn't quite as punchy.

[ Parent | on HN ]

Re:How Ravelry Scales to 10 Million Requests Using Rails by sophacles on Friday September 25, 2009 @04:13PM (#844243)

Sorry for that late reply, IMO, that title was fine, it did it's job well. My rant, etc, was about the stats section in the article itself. It still uses a flat time model, on the scale of N things/day instead of a more representative N things/day (X things/(smaller than day time unit) at peak).

[ Parent | on HN ]