<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Thanks for all your responses, I'll need to check out the suggestions. <br></span></div><div><span><br></span></div><div><span>It would make a interesting case study / talk once the team investigated the cause and solutions. For all we know at the moment, it might have been caused by something totally unrelated to RoR. Maybe there were bandwidth issues or insufficient air conditioning (yesterday was a hot day!).</span></div><div><span><br></span></div><div><span> <br></span></div><div> </div><div><i>James Cumming, CFA</i></div><br><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 5 Aug 2011 11:15:31
+0100<br>From: "Alan Buxton" <<a ymailto="mailto:alanbuxton@gmail.com" href="mailto:alanbuxton@gmail.com">alanbuxton@gmail.com</a>><br>To: "'London Ruby Users Group'" <<a ymailto="mailto:chat@lists.lrug.org" href="mailto:chat@lists.lrug.org">chat@lists.lrug.org</a>><br>Subject: Re: [LRUG] e-petitions site<br>Message-ID: <015501cc5358$9bf58c90$d3e0a5b0$@gmail.com><br>Content-Type: text/plain; charset="us-ascii"<br><br>Very unfortunate for them that the new e-petition site was launched at just<br>the same time as all the excitement about the death penalty debate was<br>happening. I would hazard a guess that this alone would have sparked many<br>more visits to their site than I think they would have expected prior to<br>go-live.<br><br> <br><br>Once the team have nailed their performance problems then hearing from them<br>what happened, how they fixed it, what they've learnt etc would make a<br>really interesting future LRUG talk/case
study. Any chance of that<br>happening? <br><br> <br><br>FWIW ref the original question - I support James Harrison's view of keeping<br>an eye on your slow pages and your slow queries and always always making<br>them faster, before they become the bottleneck. I really like the new relic<br>monitoring (www.newrelic.com) and you apparently get it for free with a<br>number of hosting companies. <br><br> <br><br>With the types of apps that I tend to do I have always found getting half a<br>dozen people with a few browsers to hammer the site (perhaps running on a<br>number of VMs) gives you a great indication of where your bottlenecks are<br>going to be. Dunno if I dare mention it on this list but I've also got HP<br>LoadRunner for some of our load tests currently (long story). <br><br> <br><br>a<br><br> <br></div></div></div></body></html>