Trex Threads Test
How many requests a SAP TREX server can process depends upon the number of threads each service of the SAP TREX server has been configured with. Without adequate threads, the SAP TREX server may not be able to service all requests, thus resulting in delays in request processing, long pending request queues, and degraded TREX performance. To avoid such anomalies, administrators will have to track the usage of threads by the SAP TREX server, proactively detect a probable contention for threads, and accordingly decide whether/not to increase the size of the thread pool. To achieve this, administrators can take the help of the Trex Threads test.
This test indicates the total number of threads each service of the SAP TREX server can spawn, reports the number of threads that are running, idle, suspended etc for each service and thus reveals whether/not the SAP TREX server needs to be configured with more threads to handle its current task load and to shorten the request queue.
Target of the test : A SAP TREX
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each host:service of the target SAP TREX server that is to be monitored
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Stat request threads: |
Indicates the number of threads that were processing the requests for this service. |
Number |
If the value of this measure is 0, then the incoming requests to the service will not be processed. |
Idle threads: |
Indicates the number of threads that were instantiated and were awaiting incoming requests for this service. |
Number |
|
Inactive threads: |
Indicates the number of threads that were inactive for this service. |
Number |
By comparing the value of this measure across services, you can identify the service on which too many threads are inactive. |
Running threads: |
Indicates the number of threads that were running and processing the requests for this service. |
Number |
The detailed diagnosis of this measure lists the caller, called party, user, method details, running duration etc. |
Suspended threads: |
Indicates the number of threads that were suspended for this service. |
Number |
|
Sleeping threads: |
Indicates the number of threads of this service that were sleeping. |
Number |
|
Other threads: |
Indicates the number of threads that were in other states corresponding to this service. |
Number |
Other states vary based on the service to which the thread belongs to. They could be any of the following states : AssignEvent, attributeengine, connected, ControlSearchCacheEvent, createIndex, executetreequery, fdir, fput, getMemWatchInfo, getSelectedQueues, incrsyncpoints, asxml/indexCellTable, loadhistory, asxml/multiIndexCellTab, optimize, optimize/load, ping, pingstat, __PINGSTAT, pexec, preloadIndex, preloadIndex/load, prepareOptimize, reorg, search, asxml/searchCellTable, searching/lexicon, send, setIndexProperty, setIndexProperty/unload, set_index_property, show, simplestat, splitIndex, storetrees, defineConcatAttribute |
Total threads: |
Indicates the total number of threads allocated for this service. |
Number |
|