Re:buffering ......... (Score 2, Insightful)

Hey Khasim. Can I say, I have to disagree. Analysing latency on large networks is incredibly important. There are often so many latency-inducing mechanisms between a packet leaving an application and arriving at the other end (misconfigured stacks, poor cabling, misconfigured routers and switches (#1 cause!), greedy applications, messy applications, multicast floods etc etc), that it is impossible to tell what the problem is. Modern networks are straining with latency problems that added bandwidth doesn't always solve. The problem is that if you have a large number of servers and clients and there's a problem - which codebase or hardware do you upgrade? You can't tell, because you don't know who's causing the problem. Only by analysing the network can you tell. As a developer, I use wireshark for this often to find out what the trouble is - asking other coders doesn't help - only when I look at the network I can pinpoint the problem - if you fail to configure your video service properly, a group of managers having a v-conference can blot out your network. But you won't know its happening because its off in building #5 somewhere - nowhere near your main servers.