Documenting Why “Its Slow”
I can’t tell you how many times I have heard that dreaded phrase, “Its Slow”.
I’ve heard this so many times I typically casually respond with, “Great, what is it and how slow is slow?”
The biggest issue I have with this statement is that this is the typical network complaint that sucks you into the troubleshooting vortex since nothing is clearly defined.
For example, if I said, “email is slow or it takes 2 hours to download my files” you have a chance to address this since I can measure the problem and the end result. The 2 hour comment actually gives you a measurable value to compare against.
One of the toughest things about troubleshooting is when an assumption is made like drive x on the server is fine, therefore the server is fine.
In this example I wanted to demonstrate to a client that one disk or file system on a server can be slower than the other. I also taught him some Wireshark tips and tricks along the way to help him in the future.