Hacker News Reader

Don't forget that bandwidth is only half (and most of time not the important half) of the story. Latency and packet losses usually have much stronger effect on website performance (see this classic paper http://www.stuartcheshire.org/rants/Latency.html or any of velocity 2010 videos).

There are a couple of free and commercial products that enable you to emulate latency, packet loss and bandwidth at the same time, just google that.

View on HN

I saw precisely this in the (attempted) cross-continent deployment of some enterprise software. The amount of data being moved was relatively small, but the software was so damned "chatty" -- insisting on dozens of requests/responses for even the simplest operation -- that latency effectively killed it in this context.

I'd argued this point and that it be tested -- a simple network simulator would have sufficed. But management was willfully clueless, and the vendor wanted the sale more than an effective deployment.

Latency should be a part of any non-trivial testing.

Reply on news.ycombinator.com