Fileshare Performance Net Express 4.0 (Application Server)

Problem:

Fileshare is performing about 10 times slower on Net Express 4.0 than on Net Express 3.0.

Resolution:

The reason why Fileshare is slower in performance is while running with asynchronous comms, the process gets dropped by CCI, if no messages are waiting.  The fix for this is to switch the comms to synchronous using the /sc option in FS but that requires a password file to be used.

When you are using synchronous comms, it is quite tricky to shutdown the FS server, because it can take quite a while to respond to the screen.  If the FS server is idle, then it will only be checking the keyboard once every two minutes ( by default ) and so a user hitting escape will likely not get the response from it, that he expects.

In the product is an API FSMGR, which provides ways of controlling FS remotely but there is no program provided.  You have to create your own or use something like the FSVIEW addpack.

The solution to the performance problem is as follows:

fs /u FSVIEW /pw FSVIEW /pf FS

fs /pf FS /s FS01 /sc /t 0

When doing it via the command prompt it will look like follows:

setlocal

FS /u FSVIEW /pw FSVIEW /pf FS.dat

endlocal

setlocal

fs /pf fs.dat /s FS01 /sc /t 0

endlocal