As your company builds the software and hardware infrastructure inside your enterprise, new systems are typically layered on top of old ones. In fact, there could be systems in place which were put there long before you got there and which you have no knowledge of, yet which could be having an impact on performance. If it’s your job to make sure the system is performing optimally, you have to know as much as you can about your overall architecture as possible.
That’s where monitoring tools can come into play. You could find out for instance that a single transaction invocation could be making 5000 SQL database calls and in the process is sucking resources without your knowledge. When you figure out where these “chatty transactions” are, you can get your team together and figure out why it’s happening and take steps to fix them.
The fact is that there’s so much going on inside your company, it’s impossible for one team to be aware of every little thing, but when you begin monitoring in earnest, you may suddenly realize that there are a couple of areas that are really spiking in terms overall usage and those are areas where it’s worthwhile to attack to increase your overall performance.
The point of all this is not to scare you. IT pros who have been around the block a few times won’t be intimidated by this knowledge, but you need to get a grip of what’s going on across your entire infrastructure in order to bring these resource sinks to the surface.
Finding the problem is just the first step of course, but you can’t improve overall system performance without understanding how data flows through the system and where it might be stalling or slowing down.
Once you understand that something is causing the system to bog down, you can begin the work to fix it. It could be a matter of figuring out how to reconfigure the program to work more efficiently or you might need to dedicate more resources to the process so it can scale up to deal with the traffic you have on it. It even could be just a matter of sloppy programming in which case, you might have to go back to your developers or to the vendor and ask why it’s happening and ask them fix it to run more efficiently.
But if you want to find those areas that are having the most adverse affect on your system performance, you need the proper tools to do it, and you have to understand how to read and interpret the results you are getting from your reports.