Most of us are using Web2.0 sites but massive user base that logins every second is a big challenge to system performance. Let’s see how engineers working for MySpace, Facebook and Twitter are doing their job.
Note: all uptime buttons and images below are generated in real-time, you can click on images / baners to see reports with details directly from site-uptime.net.
MySpace uptime
I just got an email from my monitoring system:
Site: http://twitter.com is down ('502 Bad Gateway')
Looked at main Twitter page and saw this picture:
I checked that Twitter responds very slowly and randomly shows “over capacity” page. You can see details on site-uptime public report. Here’s response graph from last days (measure interval 15 minutes, HEAD requests):
UPDATE (2010-04-15): after few weeks the situation is getting worse:
Próbowałem dziś zalogować się na GL i zauważyłem, że serwis nie działa tak jak powinien (częste “timeouty” w przeglądarce). Postanowiłem przyjrzeć sie bliżej działaniu serwera i założyłem monitor na niego przy użyciu site-uptime.net (interwał 15 minut, metoda: HEAD HTTP/1.0). Oto rezultat po dwóch godzinach monitorowania (ujemna wartość oznacza brak dostępności serwera):
Twitter is a “free social networking and microblogging service that enables its users to send and read messages known as tweets”. It’s gaining popularity last months – userbase is growing rapidly. It’s interesting to analyse Twitter’s server infrastructure load by observing service response time over few days.
site-uptime.net, network monitoring service was extended today by HTTP method selection option. You can choose to use HEAD (smaller network overhead) or GET (maximum 10 kB is downloaded in one measurement). Get option allow to download and analyse HTML content for specific keywords (required, like static text on webpage or undesirable, like IFRAME viruses).
Powered by WordPress
