Wall Street Not Alone In Crashing Tuesday
Written by Evan SchumanThe abrupt 200-point plunge in stock prices this week sent investors running to sell shares and Web admin struggling to keep sites from crashing.
As people looked at the incredible strain placed on Web servers this week when the market took a massive tumble, a frequently-heard comparison was with retailers fighting holiday shoppers.
There are two reasons such a comparison doesn?t work. First, the start and likely end of E-Commerce heightened purchases are precisely known and known for more than a year in advance. Tuesday’s plummet came with no warning.
The second reason, though, involves consequences. A consumer shopping who is delayed a couple of minutes will be annoyed and perhaps might even jump to a competing site. An investor who is similarly delayed?especially around the 4 PM Cinderella hour, when carriage share sales orders turn into pumpkin powerless keystrokes?can literally lose a fortune. And, of course, most investors are locked into using one broker (wherever their accounts reside) and they can’t switch on a whim when server performance slows, pointed out Abelardo Gonzalez, a Web performance manager at Keynote Systems.
How slow did things get? Well, that depends on the site examined. After all, it’s times like these that separate the men from the bulls.
The two top firms that track Web traffic are Keynote and Gomez. Although the two firms’ methodologies differ?making direct comparisons difficult?both agree that eTrade did quite well during the trading onslaught, while investment houses with much longer histories?including Fidelity Investments and Vanguard?fared poorly.
But again, how poorly? On a good day, the typical trading site should respond with a few seconds. A day before the plunge (Feb. 26), for example, Gomez found Scottrade responding with an average of 3.7 seconds, ETrade at 4.6 seconds, TradeKing at 8.5 seconds with old-timers typically delivering weaker figures, with Charles Schwab at 11.5, Vanguard at 11.5, Fidelity at 19.4 and Wells Fargo at about 22 seconds. Please remember those are typical figures for the day beforethe plunge.
On the day of the plunge, it wasn’t only stock prices that were on a freefall. Vanguard’s 11.5 second response dropped to an amazingly bad 208.43 seconds. Yes, that’s almost 3.5 minutes. That’s just an average. Gomez clocked Vanguard as slow as 350.2 seconds, which is almost six minutes.
Imagine trying to execute a trade and having to wait almost six minutes for the site to respond. Do you assume the site has crashed? Do you dare try again, risking a double order?
Vanguard was the worst on Gomez’s radar, but Fidelity (with an average 96 second response time) and Banc of America (averaging at about 82 seconds) held their own in the lousy response department.
Why the difference? Matt Poepsel, vice president of performance strategy at Gomez, believes much of it involves upbringing. eTrade and some of the other younger sites “really cut their teeth on the Web. The understand the importance” of response time and “they built their infrastructure the right way.”
The challenge for some of the larger sites also involves the inability to solve these kinds of problems by throwing money at it. “There are certainly some things you can do with capacity, but there are not an unlimited number of things you can do,” Poepsel said.
Keynote’s Abelardo Gonzalez pretty much agreed, although Keynote released very few specific performance numbers. “Fidelity did have places where they went over 40 seconds. The slowest was about a minute,” he said.
Gonzalez said that although response times are critical, he thought a potentially even more important number to watch are failed transactions, citing the day showing a 25 percent decrease in successful transactions.
Keynote also cautioned Web managers to not draw the wrong conclusions. Some site managers want to look at the worst performance they’ve seen and load-test for double that. Gonzalez suggested that testing for seven times the peak figure might sometimes make more sense.
On the one hand, it’s easy to dismiss weak site performance during these market plunges as inevitable, on the rationale that Web sites must prepare for what is reasonable and likely. Paying for an infrastructure that is designed to assume that every day is a mad rush wouldn’t be very responsible, the argument?typically advanced by people who think cheapness is a virtue?goes.
That argument might sound convincing were it not for the existence of sites like eTrade. They prove that it can be done and not necessarily with a break-the-bank budget. How often have young Web operations found ways to deliver performance in a way that the established companies simply knew couldn’t be done?
Giving an online site a true Web-centric architecture, infrastructure and attitude? Now that’s a gameplan I’d invest in.
Cards issued by European banks when used online cross border don't usually support AVS checks. So, when a European card is used with a billing address that's in the US, an ecom merchant wouldn't necessarily know that the shipping zip code doesn't match the billing code.
-Marc
