Has anyone monitored nserver.exe utilization for either a client/server driven process that runs a Java agent which makes a call to a Servlet on another server?
Basically, the client follows a set of steps. If the program logic deems necessary, the client calls a Java-based agent, which runs on the server. This Java-based agent, calls a WebSphere Servlet in order to obtain information from another system.
The servlet is fed 4-5 parameters and performs a lookup against another application to return a set of data. The time to run the servlet outside of Domino is 2-3 seconds at the most.
There is also a background agent, that runs on a schedule, and scans the database for documents that need to be updated as well - hopefully to save the end-user from having to wait 10-15 seconds while the Java agent finishes.
In every case, whether the client drives the process or the scheduled agent, with either both processes in place or only one of the processes in place, the Server Utilization drops to 0% available during the time required to call the Servlet and a few seconds thereafter.
The load affects end-user performance significantly and I wanted to see if anyone has found a way to instruct Domino to make this process less intense. It appears that nserver.exe is taking the hit, not the amgr.exe task.
Even if I disable the client driven code and just let the scheduled agent handle the work, each time the agent runs, end-user performance is effected.
We are using Domino 6.5.2 as a Service on brand new HP server running Windows 2000 with Service Pack 3, 3 GB of RAM and 4-3GHz CPUs. During this entire time, Windows 2000 indicates the server is only 20-30% utilized.
Has anyone seen this type of issue, possibly finding a work-around?
We have even tried to set nserver.exe as the highest priority with Windows 2000’s Task Manager, without any luck.
Thanks for your time!
jv