Question
Anthem, Inc.
US
Last activity: 17 Mar 2023 5:27 EDT
Max Active Requestor Configuration is not matching in Requestor Pool of Admin Studio
I have configured my Maximum Active Requestors in service package as 60 and Idle as 10. We have 2 nodes processing the requests and in the Requestor Pool of Admin studio I can see only 15 in Active and 1 Idle on each node. Am I missing any configuration? Any idea why it is not going above 15.
Areteans Technology Solutions Pvt. Ltd.
IN
@SravanthiM2905 There is no problem with your configuration, in here idea is if all the 60 requestors are active at a time then you might be able to see the 60 count there. But in normal situation based on the current pool utilization the count will be shown. To get more and better understanding you can go to the tripple . option at the end of your row and click there you will get option to view more details in that link you will be able to see the correct utilization of your configured requestor pool.
Hope this help to address your concern.
Anthem, Inc.
US
@AmarTiwari Thanks for the response.
The problem is that even during the peak times in PROD (where Maximum Active Requestor is configured to 40), the active requestor is not reaching 40. Please find the screenshot attached for reference taken from options. I wanted to understand why that is always 15 or 16 at the max.
Proximus
BE
At first sight you're not hitting your maximum and your called requestors are released back to the pool quickly enough to be re-used. I would say that there's no issue here and that your design is correct.
Why do you want to see your maximum hit? Do you face an error not visible as per the requestor pool screen?
If there's an environment where you can do some testing, put the max to low value and decrease the allowed waiting time.
You'll see that this generates errors.
Regards
Anthony
Anthem, Inc.
US
@Anthony_Gourtay Hi Antony, Thanks for your response
To your question "Why do you want to see your maximum hit?"
Because even during the peak hours where I am expecting to see the usage of maximum requestors(set to 40) is never reached; not even close. Only 15 out of 40 is being used on my service package. I feel that the Requestors are not being used in full and as a result it is slowing down the performance. I would like to know if there is any configuration that I am missing which is causing the requestors not being utilized or is that the expected behavior.
Proximus
BE
Hello,
Your slowness could be from before the service package.
I don't know what triggers the call of this SP but if the message picker process has limited threads then it won't be able to do more calls to your SP and slowness will be at the entry and not during the processing.
Then you should also check your max prpc workmanager defined at application level to be sure your SP can still create new requestors.
I would reduce the max wait time of 3 minutes. This is pretty high. Make it 5 or 10 seconds and see whether there's any change in behaviour.
Last, it's indeed strange that you seem always stuck at 15 max.
During your peak & slowness time, isn't there any message in logs for workmanager or for this SP or at DB connection level or anything else which could globally slow down the application hence the SP also?
Regards
Anthony