Analysing Ping

With the slowed working of the database, the speed of connection with the server must be checked. That is why there are several parameters available, which help us diagnose the problem.
The most important parameter is the so-called 'ping time' which tells us if the IP address of the server exists or if it is accessible, and how long data travels from the server to your work station.
 |
WARNING
- The ideal time is under 20 milliseconds, but if it is over 100ms, the connection must be checked with the internet provider.
- If the result of the ping is 'No response', the server is not available (it is not working). In that case, turn to the person overseeing the server performance.
|
The Ping/Trace panel can be accessed by clicking the Performance panel, located in the Administration panel.
 |
HINT
On the Ping/Trace panel, we can check the performance speed (ping) for the available Datalab services:
- Edgar
- DMS
- DMS Link
- Hosting IP
- UserSite
|
 |
CASE SUMMARY
Accountant Ashley carries out regular work tasks in the program, but the processes after clicking are carried out much slower than usual. Because of this, she informs the IT department of this situation. The person responsible from the IT department first checks the basic web connection performance parameters, in this case the Ping parameter.
The person responsible does this in the following way:
- Pinging the server
- Interpreting ping results
|
The person responsible from the IT department first wants to check the performance speed of the connection to the Edgar server.
For this purpose, the person responsible opens the Ping/Trace panel and clicks the
button.

The program returns the result.
In the second step, the person responsible checks the returned results of the ping.

The person responsible sees the following in the Ping log:
- A ping of the server with the IP address 91.199.61.60 was carried out;
- a 32bit-sized data package has been sent;
- the first server response was returned in 1ms and the secon in 0ms.
Since the result is appropriate (the optimal response time to the ping is under 20ms), the person responsible dismisses the possibility that the slow performance of the database was caused by the Ping parameter.
 |
HINT
If the Ping parameter is correct/suitable, continue with analysing trace
|
 |
HINT
In the same way, the person responsible carries out the ping analysis for all available Datalab services:
- Edgar
- DMS
- DMS Link
- Hosting IP
- UserSite
|