[deleted]
37Signals benchmarks uptime vs five leading webapps
21–30 of 34 posts
Re: 37Signals benchmarks uptime vs five leading webapps
#22This is one of those posts that drives me a little crazy :P We recently started a web monitoring company (in beta) http://www.verelo.com to tackle situations just like this. Pingdom monitors every 60 seconds, its just not enough if you want to make claims like "we were only down for 6 minutes". If you want to make claims at a single digit minute level you need to check more regularly, and your checks need to be robus…
I use Pingdom, but wish they could monitor more frequently for exactly the reasons you mention. In theory my site can be unavailable for several seconds each minute, without showing downtime in the stats. I signed up for your service, but looks like it is invite only right now?
Re: 37Signals benchmarks uptime vs five leading webapps
#23I am curious on the choices of the 5 companies to compare against. The amount of load a site deals with is an important factor when comparing uptime.
Re: 37Signals benchmarks uptime vs five leading webapps
#24Earlier quoted context omitted.
We configured all the benchmark apps to expect a response. So on Github we go and checkout a repo. On Freshbooks a known invoice. On Assistly the agents index. Etc. This is "the app is functional" checking. Not just 200 OK.
The most reliable measure of true uptime would be transaction monitoring, e. g. simulating a login into all of these web apps. It also catches those issues were the server itself is up but the site does not work for some other reasons (database issue, javascript issue,...). Or do you know that all your downtime was "total downtime", i. e. server not reachable at all?
We do more than just login to the apps. We login and go to an expected spot. So it catches all of that.
This includes total downtime yes.
Re: 37Signals benchmarks uptime vs five leading webapps
#25This is one of those posts that drives me a little crazy :P We recently started a web monitoring company (in beta) http://www.verelo.com to tackle situations just like this. Pingdom monitors every 60 seconds, its just not enough if you want to make claims like "we were only down for 6 minutes". If you want to make claims at a single digit minute level you need to check more regularly, and your checks need to be robus…
Sounds good! Remember to setup transaction tracking, though. Just doing pings or http get and expecting 200 OK on a page is not enough for this to be interesting.
For Basecamp, we login, go to a project, and post a message, or something like that. So you catch as much as possible.
Re: 37Signals benchmarks uptime vs five leading webapps
#26Looks like 37signals changed a bit in 6 years : http://37signals.com/svn/archives2/dont_scale_99999_uptime_i...
We certainly have! I would be embarrassed if we hadn't.
Also, that's why we're comparing uptime against big, established web applications. I would not hold these standards up to a 1 year-old, newly started business. You have far more important things to worry about than getting an extra 9 on your uptime.
Re: 37Signals benchmarks uptime vs five leading webapps
#27Looks like 37Signals are preparing to launch their Basecamp.Next. Y'all can see how there's been an increasing of 37Signals posts lately.
And all of them seem to make it on the homepage...
I'm looking forward to "37s uses 2 PSUs in their servers!" and "37s pushes over bag of rice!".
Re: 37Signals benchmarks uptime vs five leading webapps
#28I loved the second comment from DHH replying to GB:
I didn’t think it was a very long article? Your first comment
missed the first paragraph and your second comment missed the
second paragraph. There’s only two more paragraphs to go, so
please take a swing at them :)Re: 37Signals benchmarks uptime vs five leading webapps
#29Looks like 37Signals are preparing to launch their Basecamp.Next. Y'all can see how there's been an increasing of 37Signals posts lately.
And all of them seem to make it on the homepage... I'm looking forward to "37s uses 2 PSUs in their servers!" and "37s pushes over bag of rice!".
Hey, at least we aren't hearing about what they had for breakfast...
Re: 37Signals benchmarks uptime vs five leading webapps
#306 minutes downtime for Github? Github is amazing. That's all. :-)
That's over a 6 week period. Github's downtime over 2011 is considerably more than that!
Not only that but Github's asset server have gone down a number of times (for reasonable periods of time too) quite a few times in the past few months, rendering the frontend pretty much unusable. I suspect Pingdom wouldn't pick that up.