[LRUG] e-petitions site

[Alan Buxton]

Very unfortunate for them that the new e-petition site was launched at just
the same time as all the excitement about the death penalty debate was
happening. I would hazard a guess that this alone would have sparked many
more visits to their site than I think they would have expected prior to
go-live.

 

Once the team have nailed their performance problems then hearing from them
what happened, how they fixed it, what they've learnt etc would make a
really interesting future LRUG talk/case study. Any chance of that
happening? 

 

FWIW ref the original question - I support James Harrison's view of keeping
an eye on your slow pages and your slow queries and always always making
them faster,  before they become the bottleneck. I really like the new relic
monitoring (www.newrelic.com) and you apparently get it for free with a
number of hosting companies. 

 

With the types of apps that I tend to do I have always found getting half a
dozen people with a few browsers to hammer the site (perhaps running on a
number of VMs) gives you a great indication of where your bottlenecks are
going to be. Dunno if I dare mention it on this list but I've also got HP
LoadRunner for some of our load tests currently (long story). 

 

a

 

From: chat-bounces at lists.lrug.org [mailto:chat-bounces at lists.lrug.org] On
Behalf Of Mickael Riga
Sent: 05 August 2011 09:47
To: James Cumming; London Ruby Users Group
Subject: Re: [LRUG] e-petitions site

 

Hello,

 

Well, the simple use of `ab` utility already gives a lot of informations.

The most difficult thing is to predict your success and what is gonna be a
"high" level.

Anyway it will always be harder to build a high volume website in Ruby and
especially in Ruby on Rails.

I am sure that most of the time, the really high consuming bit could be
placed in a separate faster middleware dedicated to a specific task.

Things like APIs I mean.

But like you, I don't know what went wrong in that case.

 

mig

 

 

On 5 Aug 2011, at 09:17, James Cumming wrote:





Hi All

 

Newspapers this morning report that the e-petitions site crashed on launch,
due to high volume (1,000 visitors a minute registering proposals) . Just
wondering if it would be worth while investigating this further as to why
this happened and how to avoid something like this happening in future RoR
projects. 

 

What's the best to test a site for high volume?

 

Cheers

 

James Cumming, CFA

 

_______________________________________________
Chat mailing list
Chat at lists.lrug.org
http://lists.lrug.org/listinfo.cgi/chat-lrug.org

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20110805/3f124d18/attachment.html>