The HireTrack NX Server is powerful and very efficient, but to perform well it needs to run on a File Server machine that is also fast and efficient and not under too much stress from demands made on it by other applications. If your file server is sub-optimal you may experience poor performance in HireTrack NX and should this occur the first port of call should be to take a look at the file server and do some tests that check how well the the NX Server performs with a simulation of various number of users. To do this we have written our "Server Stress Test" application which can be downloaded from here.
There is no installation, just unzip the application and run on a workstation or remote desktop that normally runs HireTrack NX.
- We don't recommend that you run this tool on the NX Server machine UNLESS this is also your remote desktop machine (Using the same machine for the NX server & Clients is not usually recommend).
- You should not run this application while other users are using HireTrack NX: it is designed to stress the NX Server and it's host and if users are also running HireTrack then i) they will suffer unsatisfactory performance, and ii) the results of the test will be distorted.
- Depending on what options you select on the test app, it can take some time to run, anything between 3 mins and several hours!!!
Once the application is run, you will be presented with this screen:
In the Server IP box, enter the IP address of your HireTrack NX server. The Server Port & Server Name will already contain the default values for running the programme on the file server; if you are running from a workstation (recommended) change them accordingly (you would normally only set the IP address and you can find this out on the NX Server's web portal if you don't know it
Similarly the Username & Password will contain the default ones, enter yours if different.
Once entered, click the Connect button.
This will connect to the NX Server and the Selected Alias drop down will be populated.
Select an Alias. The alias is simply used as a location to store the temporary tables used by the test app. It doesn't matter if you select a live or training database, no HireTrack NX data is used. If you have aliases stored on different disks, then you may want to run the app several times, once per disk.
Next set the Max No. Clients - this is how many active users you want to test with. By active users we mean users actively using HireTrack NX, rather than just being logged in. There's usually some diversity in how your HireTrack users interact with HireTrack, so even though you might have 10 users logged in, you might have 2 prepping kit, scanning barcodes every couple of minutes as the kit is prepped, 2 returning kit via general returns, scanning barcodes continuously, someone looking at this weeks invoices, a couple of people quoting jobs and 3 people on the phone or grabbing a coffee. So from a diversity point of view, this is probably equivalent to 3 or 4 active users.
Once done, press the Run Test button.
You will get a warning explaining that this will lock up the server for a period of time. The duration given is an approximation based on an average server, yours could take longer.
Click Yes and the test will start.
The app will carry out four tests for each client a number of times. If you selected 5 for the Max no Clients, the tests will firstly be run simulating one client, then they will run again simulating two clients, then three, four & finally five. After each set of clients the scores will be displayed before the next pass starts.
The tests carried out are:
- Disk Writes
- Disk Reads
- Database Locking
Whilst a test is taking place the application will give the impression that it has locked up. Do not worry about this.
Once the first round of tests has completed, the Score will be displayed. A score lower than 5 will be displayed in Red and this indicates that the server's performance with just one client is lower than acceptable. A score of 5 or more indicates that the server is performing within spec for one user.
The graph will update after each round of tests.
When all the tests have been completed the graph will look something like this.
The score of 3 indicates that your server machine is below par, and the graph shows how much more the machine struggles as the number of users increases.