In our project we are hosting Pega as a mashup inside an external webpage of the client. As we know that Mashup gadgets works at a thread level, so everytime the mashup gadget is referred by some user actions on the host page a new thread needs to be created for the mashup gadget. We are doing so at the moment. What I would like to know if there is any limitation ( from performance and best practice) perspective to the number of concurrent open threads that we can have for one requestor session in the mashup. I know about the Pega 18 alert which comes if we have the setting on and the number of PRThreads exceeds the limit / threshold.
We are going to have performance testing conducted on the application , hence would like to know more about the restriction / best practices around managing multiple threads.