|
Measures reported by IIBThreadStTest
In the message flow execution environment, the message flow is thread-safe. You can run message flows concurrently on many operating system threads, without having to consider serialization issues.
Each input message that passes through a message flow for processing by a series of nodes executes on a single thread; it is processed only by the thread that received it. If you want to increase the throughput of a message flow, you can increase the number of threads that are assigned to that message flow. The memory requirements of an integration server are not unduly affected by running message flows on more operating system threads.
This test monitors each thread on the message flow and reports the time taken to process the incoming messages. Using this test, you can figure out how well the messages are processed and eventually identify the thread that is the slowest in processing the messages.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| avgElapsedTime |
Indicates the average time elapsed to process input messages by this thread per second. |
Messages/sec |
A high value for this measure is a cause of concern as this may be due to the processing of messages that are currently in an infinite loop. Administrators may need to check for such messages so as to maintain the value of this measure within optimal limits.
Comparing the value of this measure across the threads helps you in identifying the thread that is taking too long to process the incoming messages. |
| avgCPUTime |
Indicates the average time taken by the CPU to process the input messages. |
Secs |
|
| inputMessageRate |
Indicates the time taken by this thread to process the input messages. |
Secs |
Comparing the value of this measure across the threads helps you in identifying the thread that is taking too long to process the incoming messages. |
| messageDataRate |
Indicates the rate at which bytes of the input messages are processed by this thread. |
Bytes/sec |
Comparing the value of this measure across the threads will help you identify the thread that is experiencing slowdowns in processing the messages. |
|