| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Availability |
This measurement
indicates whether the server was able to respond successfully to the
query made by the test. |
Percent
|
Availability
failures could be caused by several factors such as the FTP server
being down, the FTP server being misconfigured, authentication
problems, file access permission problems, network failures, etc.
Temporary unavailability may also occur if the FTP server is
overloaded. |
| Total_response_time |
This measurement
indicates the total time taken by the server to respond to the
requests it receives. This time includes the TCP connection time, user
authentication time and the data transfer time. |
Secs
|
An increase in
the total response time can occur because there are too many
simultaneous requests or because of a bottleneck with any of the
applications executing on the server. |
| Tcp_availability |
This measure
indicates whether the test was able to successfully establish a TCP
connection to the FTP server. |
Percent
|
Availability
failures could be caused due to a network failure. Another possibility
is that the FTP application server is not running. |
| Tcp_connect_time |
The time taken
for the TCP connection establishment to complete. |
Secs
|
A high value
indicates a bottleneck and could be due to the reasons that the server
is being overloaded or there has been a network performance
degradation. |
| Authentication_status |
Indicates whether
the test was able to successfully log in to the FTP server using the
specified user account |
Percent
|
A low value
indicates a problem logging in to the server. |
| Authentication_time |
Time taken for
user authentication |
Secs
|
This value gives
an idea of where the performance bottleneck with the FTP server could
be. |
|
Note:
Users should be provided with appropriate permissions to read
and write, corresponding to the directories they are using. |