PTE Driver nThread Bottleneck/Incompletion. Inability to Calculate Accurate TPS for Higher nThread Runs

[wfh19926658]

BC Topology: 1 Org, 1 Peer, 1 Ca, 1 Ord on bcfab2 w/ 10 IFLs, 48Gb Memory
While attempting to drive the above topology to max TPS, I continously encountered an issue with driving the peer to max TPS or CPU utilization. I tried multiple combinations of user input parameters (nThreads, constFreq, devFreq) to achieve the highest TPS possible. Although, I noticed using an "nThread" value higher than 20 threads produced the error:

"stderr: (node:36570) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3129): undefined" For every thread running.

This error indicated that the threads were not able to complete and therefore not able to produce the "eventRegister" message necessary for calculating TPS. In terms of driving the SUT, using more than 20 threads would still allow for proper container statistics and sampler data collection, but calculating the TPS to go along with it was not possible. For example, using 50+ threads would drive the SUT to ~ 50% CPU utilization, about the highest I was able to achieve. But only when nThread was < 20 was I able to get an accurate TPS. There are a few workarounds to patching this problem but it is very inconvenient that the PTE driver cannot produce an accurate TPS for more strenuous runs. If there are any more questions about the issue/error I am seeing, don't hesitate to contact me on sametime or email me at [email protected], and thanks for the help!