CPUU product documentation does not specifically talk about executable file placement assuming that it resides on the file share with the batch file. There are some other alternatives with placing executable locally on the workstation. It may be associated with additional administrative efforts to put CPUU.exe on every workstation but is it worth it in terms of performance gain?
There are three ways of executing CPUU :
1. Locally on the workstation.
2. Through the batch file in the login script (network) pointing to the local CPUU.exe file on the workstation
3. Through the batch file in the login script (network) pointing to the CPUU.exe file on the file share on the server.
While #3 is the most easiest way #1 and #2 are obviously faster and bring some extra performance gain and less network utilization.
Here are some results received in the customer sites by field engineers. These numbers can vary significantly from site to site, and should not be used as a benchmark:
1. Batch and exe are Local - best results, CPUU process generated ~ 1400 threads, 800 Kb transmitted over the network, ~ 70 sec to execute.
2. Batch on the network share, exe is local, CPUU process generated ~ 1800 threads, ~ 1 MB transmitted, ~ 100 sec to complete.
3. Batch and exe are on the network share, CPUU process generated ~ 5500 threads, ~ 30 MB transmitted over the network, ~ 250 sec to complete.
Since CPUU is normally run over the login script then option # 2 is the most optimal.