Echoing Randall Williams and George Thompson, latency problems can be tricky to troubleshoot outside of your IT staff. I've found that IoZone is a useful tool that you can use to take ArcGIS Server out of the picture. It simulates read/write operations against a directory and measures the throughput in kb/second. You can run it against your network share and then your local directory to at least give you an idea of what your network share throughput needs to be at to perform as well as your local directory:
On the ArcGIS Server machine, install the following software:
- IOZone (http://www.iozone.org/src/current/IozoneSetup.exe)
- cygwin (http://cygwin.com/setup-x86_64.exe)
*Note, there have been issues running IOZone with paths to the network from the machine the folder is shared to, meaning running IOZone from m1 to a share like \\m1\<path>
Sign in to the Server machine as the ArcGIS Server account and run the following command from the command line:
- "C:\Program Files (x86)\Benchmarks\Iozone3_414\iozone.exe" -Ra -f //networkpath/folder/file -b %USERPROFILE%\Desktop\networktest.xls
* Ideally, the //networkpath/file parameter would be set to the share to your server directories, for example //<machine>/arcgisserver/directories/file. In this directory, it'll create a simple file called "file" and run it's tests on that file.
Run the following command as well when you're logged in with the ArcGIS Server account on that machine:
- "C:\Program Files (x86)\Benchmarks\Iozone3_414\iozone.exe" -Ra -f C:\arcgisserver\directories\file -b %USERPROFILE%\Desktop\localtest.xls
The parameters listed above are defined below:
-R = generates an Excel file
-a = uses full, automatic mode, meaning tests files with records sizes from 4k to 16M for file sizes 64K and 512M
-f = sets file path for output
-b = sets file path for Excel file.
If you're interested in knowing more about the tests that it will run, they can be read up on through the following pdf.
IoZone documentation:
http://www.iozone.org/docs/IOzone_msword_98.pdf
