Best Practices to Diagnose Windows 2003 Server Network Performance
Posted on 2010-09-02
I need to run some performance tests on our server to determine how we can improve the server's performance.
The Server is a Windows 2003 Server, running Acomba (acounting) software.
The way our company connects to this server is by mapping a network drive to that server and running the Acomba.exe application directly from the server. The amount of users on that machine has risen from 6 to about 20 users.
After speaking with the Acomba Company, they say it's the correct configuration so I cannot modify the way Acomba works, it must remain the same.
The problem is that Acomba (and an ASPX intranet site on the same server) respond very slowly to "certain" requests. (particularly when adding or editing records).
What is the Best Practice for me to determine where the bottleneck is on the Server so I can find appropriate solutions?
i'm obviously going to look into Hardware upgrades but I first need to determine how many resources are needed to provide a performing service (for Acomba and the ASPX intranet site).