Mirth Community

Mirth Community (http://www.mirthcorp.com/community/forums/index.php)
-   General Discussion (http://www.mirthcorp.com/community/forums/forumdisplay.php?f=7)
-   -   Mirth Load/Capacity Questions (http://www.mirthcorp.com/community/forums/showthread.php?t=221762)

jhansen 11-21-2019 08:34 AM

Mirth Load/Capacity Questions
With a current monthly load of 4+ million HL7 messages per month and plans to grow…

What is the recommend about of CPU/RAM required for a dedicated MS SQL Server to support Mirth Connect?

At what point (message count) should we consider upgrading from Community Edition to a Mirth Appliance? What version/level of Mirth Appliance should we peruse based on monthly message count?

As our customer base grows, we are also interested in clustering to improve up-time during maintenance windows. What would be the best version/level in this regard as well?

Thank you for your input!

kirbykn2 12-03-2019 07:48 AM

It depends.......

I have not seen anything out there that equates message volume to server resourcing. This is probably because the processing is so dependent on your channel configuration and what you are doing with Mirth.

We process about 25 Million messages per month. This is a mixture of SFTP, AWS, Webservice, direct database connections, etc. Processing EDI, HL7, FHIR bundles, and Bulk Data Extracts.

We run a single Mirth VM
  • 6 CPUs
  • 12 GB RAM
  • 1 TB for the MC database on an MS SQL server

We track are system utilization and plan capacity based off of that.

Hope this helps

jack.downes 12-04-2019 12:35 AM

Varies greatly...
you can move a lot more straight ADT from A->B than performing a ton of sequential row lookups and forwarding off that.

We move about 700k messages in a month. Because we are so small and so remote, we have a load balanced set of mirth engines running via HAProxy.

FYI we proxy SQL Server with HAProxy. People told me it can't be done, but they were wrong. We use CloudWave, and they are rather fun to deal with on Firewall changes, so we just have the HAProxy IPs (load balanced) have the hole via the firewall, and then everything needs to connect to the data repo, hits the proxy. HAProxy for the win.

back to Mirth - we don't process much, but uptime is critical - and ease of maintenance is a wonderful thing! I can take one down, do updates to the server, bring it backup, take the other down, do the updates, etc. No downtime... in fact, we've never had a downtime that was not intentional with our mirth systems. the mirth product is remarkable!

pacmano 12-04-2019 06:36 PM

We intentionally never use the appliance since it prevents you from using a potentially rich set of tools that run natively on the operating system (in our case Linux). However we do license Mirth connect - the core license pack is really a steal. Appliance or not, it's channel history and SSL plugins are worth the asking price alone.

For a larger install we run on AWS, 4 CPU, 16Gb memory with postgres as mirth's DB engine running on a different server.

sphelan 12-12-2019 06:12 AM

For those that have responded, how many channels do you have?

We have around 500 channels and process a million or so messages a month. Messages are either HL7 or CCDA.

We currently run on one instance but are trying to figure how much is too much for one instance.

kirbykn2 12-12-2019 06:16 AM

We have around 140 channels and process 25 million messages per month. Monitoring the performance trends on your server should help to give you an idea of when how much is too much for one environment.

All times are GMT -8. The time now is 05:56 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Mirth Corporation