Announcement

Collapse
No announcement yet.

Mirth Load/Capacity Questions

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 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!

  • #2
    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
    Best,

    Kirby

    Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

    Appliance Version 3.11.4
    Mirth Connect Version 3.8.0
    Java Version 1.6.0_45-b06
    Java (64 bit) Version 1.6.0_45-b06
    Java 7 (64 bit) Version 1.7.0_151-b15
    Java 8 (64 bit) Version 1.8.0_181-b13
    PostgreSQL Version 9.6.8

    Comment


    • #3
      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!

      Comment


      • #4
        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.
        Mirth 3.8.0 / PostgreSQL 11 / Ubuntu 18.04
        Diridium Technologies, Inc.
        https://diridium.com

        Comment


        • #5
          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.

          Comment


          • #6
            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.
            Best,

            Kirby

            Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

            Appliance Version 3.11.4
            Mirth Connect Version 3.8.0
            Java Version 1.6.0_45-b06
            Java (64 bit) Version 1.6.0_45-b06
            Java 7 (64 bit) Version 1.7.0_151-b15
            Java 8 (64 bit) Version 1.8.0_181-b13
            PostgreSQL Version 9.6.8

            Comment

            Working...
            X