Difference between agent/threadpoolsize and app server thread pool size
Our application relies heavily on agent processing. We are planning to increase the thread pool size based on the no.of jvm's, heap size and agent parallel processing. There are two thread pools often referred in pega application context,so please let me know the difference between prconfig or DSS setting of agent/threadpoolsize and application server level thread pool size.
agent/threadpoolsize (starting with 100 for production systems and tune as needed) is pega specific setting only applicable for war deployment - which controls number of Pega-Batch threads for agent processing. On the other hand, application server level thread pools have many variations (normally there are many thread pools) - they have no direct relationship to this agent thread pool from pega. For ear deployment, Pega utilizes application server JMS (for JBoss/Weblogic) and WorkManager( Websphere) for agent processing. Starting from Pega 8.x, Pega introduces queue processor for background processing, which is the long term replacement of legacy agent processing. See https://community.pega.com/knowledgebase/queue-processor-faq for some details. One of the biggest advantages of this approach is that it is application server agnostic among others. You do not need to a JEE expert to grasp the queue processor concepts.