Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.
Lessons on how Yahoo! Japan generates enough traffic to bring a host down
Posted on 3-Mar-2005 09:00 by M Freitas | Tags Filed under: Blog



In the last two years we have been linked from some heavy-weights in the on-line world, including having two articles showing on the Slashdot frontpage at the same time. But nothing has prepared us for what happened on 1 March. Suddenly one small article about a new mobile phone was picked up by Yahoo! Japan and posted on their news page. This was during the business hours in Japan, around 4pm in New Zealand.

This shows the power of branding. The article in question is about a new Sony Ericsson mobile phone with the "Walkman" brand in it. Put "Sony" and "Walkman" in one article about a new product, and you have a mix that can potentially drive masses of Japanese readers eager to know more - and bring down a database server.

During the next two hours, the Microsoft IIS and Microsoft SQL services hosting Geekzone had to provide resources for a traffic load that was more than 15 times our average number of pages served per hour. This wasn't spread over the day, but concentrated in a shorter period of time. That single article was viewed by more than 120,000 users in a couple of hours - in addition to our normal traffic.

During this time I had to contact my hosting provider (Intellihost, a service from Iconz) to arrange for the SQL server to be restarted, since it had stopped responding to the ASP engine and to the SQL Query Analyzer tool - such was the volume of transactions going on! I have to say I always had a good service from the support folks working at Intellihost. They also seem to be always in good mood.

Things were under control after a few minutes, and showed the importance to prepare a plan to such events. I am not sure what the next steps are. Most likely someone will suggest a collocation service, database fine tunning - and these options are not out of the cards. The problem is cost going up with hardware expense, environment hosting and of course the server software. And there's the problem of "average". This event is not the average traffic, just a peak.

How we manage this? Just let this happen, or prepare for a huge traffic - that may never come again?






comments powered by Disqus


Trending now »

Hot discussions in our forums right now:

Hopeful signs from Netflix
Created by Rikkitic, last reply by networkn on 23-Jan-2018 21:14 (23 replies)
Pages... 2


No Dial Tone From Wiring Bridged Telecom Module (HBG-1008)
Created by Yoban, last reply by SATTV on 21-Jan-2018 16:49 (16 replies)
Pages... 2


Vodafone prepay auto-renew
Created by bagheera, last reply by bagheera on 23-Jan-2018 13:15 (13 replies)

What is the New Cable Going to Mean for NZ?
Created by Pumpedd, last reply by PhantomNVD on 21-Jan-2018 01:35 (36 replies)
Pages... 2 3


Boat electrics help with 2x12v batteries
Created by Hatch, last reply by Hatch on 23-Jan-2018 20:27 (11 replies)

Sulphur in petrol
Created by Rikkitic, last reply by kryptonjohn on 23-Jan-2018 14:27 (9 replies)

Galaxy S8 losing UMTS 3g connectivity
Created by Alan2, last reply by matisyahu on 22-Jan-2018 15:13 (19 replies)
Pages... 2


New laptop, battery full charge capacity already down to 96% original according to HWMonitor
Created by paulchinnz, last reply by Batman on 22-Jan-2018 11:54 (9 replies)