Show TOC

Server-Related InformationLocate this document in the navigation structure

Use

The Services window displays the load on the TREX servers and information about them.

Features

The information is displayed in a table. There is a separate row for each TREX server.

The columns contain the following information:

Column Description

Active

Specifies whether the TREX server is available

Location

Machines that the TREX servers are running on and the TREX server ports

Services

Type of service

Process ID

Process IDs of the running TREX processes.

The TREX RFC server can be configured so that more than one instance runs. The column then displays the corresponding number of process IDs.

CPU Usage

CPU load.

  • Green: 0 - 70 % load
  • Yellow: 71 - 85 % load
  • Red: more than 85 % load

If the CPU load is more than 70 % the system status may be critical. However, it may also be the case that the system was deliberately configured to allow such a load.

For detailed information on CPU load, use operating system methods such as the Windows Task Manager.

Memory Usage

Memory load.

  • Green: 0 - 70 % load
  • Yellow: 71 - 85 % load
  • Red: more than 85 % load

The higher the memory load, the slower the processing.

A very high load can indicate a critical system status. This may occur if a process takes up almost the maximum amount of main memory. Depending on the operating system configuration, the maximum lies between 2 and 3.75 GB per process.

Resp. Time

Average duration of a request in seconds.

If a TREX server has the value 0, it has not received any requests. This might indicate that the TREX server is configured incorrectly.

In the case of a distributed TREX system, the absolute value of a TREX server is less interesting that its value in comparison with other the TREX servers. For example, you can check whether all index servers have similar values. If this is the case, the load is equally distributed among the index server.

Request/Sec

Average number of requests processed by a TREX server per second.

Finished Req.

Number of requests that the TREX server has processed since it was started.

Active Req., Pending Req.

Number of requests that a TREX server is currently processing and that are waiting to be processed.

If the values in these two columns are particularly high, the TREX server may be overloaded.

Server Info

Specifies the name and details of the connection

If a row does not contain any values, the TREX server has not returned any values to the TREX admin tool. Possible reasons are:

  • The TREX server is not available
  • The TREX server is overloaded

Activities

You can restart a service by selecting the row in question and choosing Restart.