Posted: 7 Oct 2020 21:43 EDT Last activity: 8 Oct 2020 6:59 EDT
Community has quite a few questions regarding threadpoolsize but no one - pega/members have been able to answer this question to the satisfaction. I've also reached out to few people in my circle but everyone has different understanding of it so it would be nice to get some official response on this.
So how does agent/threadpoolsize really works?
1. Is it 5 (default) concurrent threads per agent as in if there are 20 agents running and each agent has 5 items in the queue to process, then x 5 = 100 threads/batch requestors are processing different queues on a node? Taking example of FTSIncrementalIndexer does it then only process 5 items at a time for search indexing?
2. Is it regardless of number agents running, only 5 concurrent threads can be run. Considering there are so many OOTB agents does this mean agents wait for each other to finish and those 5 thread be available to others? I doubt this to be true as this would be detrimental to the app performance.
3. Is this setting in play only in the context of standard agents/queue processor?