No announcement yet.

NextGen Connect - server requirements

  • Filter
  • Time
  • Show
Clear All
new posts

  • NextGen Connect - server requirements

    I wanted to get an idea of what others were doing for their Mirth Connect setup, in terms of RAM and Disk Space they have allocated.

    Planning on deploying to CentOS VM

  • #2
    That a very broad question. Maybe list more attributes about message volume, kind of channels, where mirthdb sits, on an on.
    Mirth 3.8.0 / PostgreSQL 11 / Ubuntu 18.04
    Diridium Technologies, Inc.


    • #3
      Vmware Vm :
      windows server 2012 R2 Std
      MySQL 5.7
      JRE 1.8
      vCPU : 2 (<5% used)
      RAM : 4 Go (83% used)
      3 HD: 50Go system, 100Go (data+database) and 100Go Archives
      19 channels (with filters and transformations)
      around 900 000 messages processed till now
      Hope this helps


      • #4
        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


        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


        • #5
          +1 for CentOS and a ton of RAM. "Speed" is almost entirely dependent upon the speed of the database, so use a RAID array of SSD disks whenever possible!

          -= Jack Haines : Founder/CEO of Healthcare Integrations, LLC
          -= [email protected]
          -= Mirth Connect (Advanced)-certified
          -= Gold member of
          -= Available for Mirth Connect channel development and consultation! Schedule a FREE call with me at


          • #6
            We run multiple Mirth instances on the SmartOS platform.

            So, Solaris Zone
            3G ram
            3G swap
            Since it's a zone, we've only chosen to limit ram. THis is for us and controlled by us, so I know what all is using drive and cpu, both of which are unlimited usage for the VMs.

            I know Java likes ram - but we handle only about 700k msg/month, and I'm running twin instances, so that's about 350k msgs per month each... 3G ram is enough for that.

            Database is a common Postgresql setup. 9.6.11. uptime on that is 814 days, lol. It's running in a ZFS backed VMWare setup. 32G ram for the database. drive throughput is just fine for our needs. overkill really.
            Last edited by jack.downes; 12-03-2019, 11:49 PM.