eG Help

How many requests an MDM server can process depends upon the number of threads it has been configured with. Without adequate threads, the XenMobile MDM server may not be service all requests, thus resulting in delays in request processing, long pending request queues, and degraded XDM performance. To avoid such anomalies, administrators will have to track the usage of threads by the MDM 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 XDMThreadTest test.

This test indicates the maximum number of threads the XDM server can spawn, reports the percentage of threads currently in use, measures the length of the outstanding request queues on the XDM server, and thus reveals whether/not the XDM server needs to be configured with more threads to handle its current task load and to shorten the request queue. In addition, the test alerts administrators to any increase in the number of threads with errors.

Measurement	Description	Measurement Unit	Interpretation
min_thread	Indicates the minimum number of threads that should be available.	Number
max_thread	Indicates the maximum number of threads that the server can spawn.	Number
pool	Indicates the number of threads by which the pool size has been increased since the last measurement period.	Number	A significant increase in the value of this measure is indicative of an increase in the load on the XDM server.
crnt_thread	Indicates the number of threads currently active.	Number	This is a good indicator of the current load on the server.
watng_thread	Indicates the number of threads that are waiting currently.	Number
active_thread	Indicates the number of threads that are currently active.	Number
perc_active	Indicates the percentage of threads that are currently active.	Percent	If the value of this measure is close to 100%, it could indicate that the server is about to utilize its entire thread pool. Under such circumstances, you can consider increasing the maximum number of threads that your server can spawn.
task_cnt	Indicates the number of tasks currently running on the server.	Number
queue_len	Indicates the current length of the request queue.	Number
wrk_queue_len	Indicates the current length of the working queue.	Number
queue_size	Indicates the total number of items in queue since the last measurement period.	Number	A consistent increase in the value of this measure could indicate a processing bottleneck on the server. Check the value of the perc_active measure for the server to determine whether the lack of sufficient threads in the server's thread pool is the reason for the bottleneck. If so, you may want to increase the ‘maximum threads’ setting for the server.
ran_gwth	Indicates the number of threads that ran during the last measurement period.	Number
err_gwth	Indicates the number of threads with errors during the last measurement period.	Number	Ideally, the value of this measure should be 0 at all times.
can_gwth	Indicates the number of threads that were cancelled during the last measurement period.	Number
pack_gwth	Indicates the number of packets processed during the last measurement period.	Number