Max processing threads

10-08-2019, 12:27 PM

I have a channel that has channel reader.
Max processing threads set to a high number, but the channel still seems
to be processing one at a time instead of creating threads and doing them all
at the same time. What should I look for to resolve this? I didn't find the bottleneck yet.

Comment

We made some tweaks in hopes to fix this.
a) Did a PGtune on the postgres db (changed settings, increased connections)
b) Found an increment leak in the global pre-processor and fixed that.
c) Fixed some channels that did not clear global channel map on deploy.
d) Increased the connection pool size in mirth for it's posgres db.

Comment

Apparently mirth connect actually instantiates the entire thread max count into memory.
Since I set this to a high number like 400 or 800. The CPU was so busy with managing all these resting threads that it became a bottleneck and our system kept failing.

Mirth need to rename that field to Instantiated threads instead of Max thread count.

We have been fighting with this issue for days because we also have a lot of channels and added multi-threading.

We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.