[23646/91][Mon Jul 08 2019 15:15:01][CServer.cpp:4636][INFO][sm-Server-02000] System Statistics
[23646/91][Mon Jul 08 2019 15:15:01][CServer.cpp:4640][INFO][sm-Server-02010] Available file descriptors: 4096
[23646/91][Mon Jul 08 2019 15:15:01][CServer.cpp:4653][INFO][sm-Server-02020] Thread pool limit: 54
[23646/91][Mon Jul 08 2019 15:15:01][CServer.cpp:4673][INFO][sm-Server-02030] Thread pool: Msgs=91073937 Waits=41590741 Misses=233924149 Max HP Msg=331 Max NP Msg=115 Current Depth=307 Max Depth=334 Current High Depth=307 Current Norm Depth=0 Current Threads=54 Max Threads=54
[23646/91][Mon Jul 08 2019 15:15:01][CServer.cpp:4681][INFO][sm-Server-02040] Connections: Current=1385 Max=1736 Limit=3328 Exceeded limit=0
Hi all,
i am reviewing stats on one of the policy server in the customer production environments, and in particular i am looking at:
Msgs= 91073937 (about 91M)
Waits= 41590741 (about 41M)
Misses= 233924149 (about 233M)
Due to the huge number of Misses, probably the 54 threads are too much.
Moreover, what sounds strange to me is the big difference (about 50 millions) between the Msgs and the Waits. I read somewhere that a policy server normal behaviour is number of Msgs about the same number of Waits coupled with a low number of Waits.
So how came up to this big difference?
I know that If a worker went to get a request from the queue to process, but had to wait for one to arrive , the Waits is increased by one.
But, in case the worker went to the queue and immediatly (no wait) find a request to process, is the request processed and the Waits is NOT updated? Am i right?
Otherwise, what could be another reason to explain the big difference between Msgs and Waits?
Best Regards
Claudio