Aurora Integration Engine 2.5.1:
performance measured, not claimed.
Full campaign from 30 October to 2 November 2026: 144 MLLP sweep steps against Mirth Connect 4.5.2 on the same bench and five eight-hour runs. Every ACK verified, every delivery reconciled with the destinations.
- 0
- messages lost out of more than 3 million in the eight-hour runs and the 144 sweep steps
- up to 6.5×
- messages per second compared with Mirth Connect 4.5.2 PRODUCTION on the same bench (2.0× to 4.5× compared with RAW)
- 4.1 ms
- median ACK latency at 100 messages per second for eight hours (ADT)
- 3,020 msg/s
- highest throughput measured (simple ADT forwarding, 32 connections)
01 · MLLP sweeps
MLLP sweeps: Aurora and Mirth Connect on the same bench
Four channels (simple forwarding and clinical channel, 0.6 KB ADT and 3.1 KB ORU), 1, 4, 16 and 32 persistent connections in a closed loop, 5 seconds of warm-up and 20 measured seconds per step, three independent repetitions (median). Only a message with a correct AA ACK and all deliveries verified counts. Mirth Connect 4.5.2 with a 2 GiB heap, RAW and PRODUCTION storage; Aurora 2.5.1 with a 4 GiB heap and STANDARD trace.


Successful messages per second (median of three repetitions)
| Channel | Conn. | Aurora 2.5.1 | Mirth RAW | Mirth PRODUCTION | Aurora / RAW | Aurora / PRODUCTION |
|---|---|---|---|---|---|---|
| Simple ADT | 1 | 482 | 139 | 86 | 3.5× | 5.6× |
| 4 | 1,549 | 433 | 259 | 3.6× | 6.0× | |
| 16 | 2,941 | 811 | 484 | 3.6× | 6.1× | |
| 32 | 3,020 | 671 | 463 | 4.5× | 6.5× | |
| Simple ORU | 1 | 348 | 109 | 70 | 3.2× | 5.0× |
| 4 | 1,137 | 333 | 208 | 3.4× | 5.5× | |
| 16 | 1,773 | 620 | 388 | 2.9× | 4.6× | |
| 32 | 1,707 | 525 | 372 | 3.2× | 4.6× | |
| Clinical ADT | 1 | 198 | 95 | 52 | 2.1× | 3.8× |
| 4 | 716 | 300 | 149 | 2.4× | 4.8× | |
| 16 | 1,074 | 455 | 247 | 2.4× | 4.4× | |
| 32 | 1,064 | 389 | 212 | 2.7× | 5.0× | |
| Clinical ORU | 1 | 157 | 78 | 46 | 2.0× | 3.4× |
| 4 | 611 | 242 | 128 | 2.5× | 4.8× | |
| 16 | 915 | 380 | 208 | 2.4× | 4.4× | |
| 32 | 889 | 371 | 190 | 2.4× | 4.7× |
ACK latency, median / 99th percentile (ms)
| Channel | Conn. | Aurora 2.5.1 | Mirth RAW | Mirth PRODUCTION |
|---|---|---|---|---|
| Simple ADT | 1 | 1.8 / 6.7 | 6.7 / 13.0 | 11.1 / 18.7 |
| 32 | 8.4 / 33.5 | 46.0 / 85.2 | 66.7 / 117.3 | |
| Simple ORU | 1 | 2.4 / 7.4 | 8.4 / 15.1 | 13.3 / 22.0 |
| 32 | 15.9 / 48.5 | 58.8 / 104.9 | 82.7 / 142.8 | |
| Clinical ADT | 1 | 4.1 / 18.5 | 9.9 / 17.5 | 18.5 / 29.5 |
| 32 | 26.0 / 87.6 | 79.1 / 146.4 | 144.8 / 273.9 | |
| Clinical ORU | 1 | 5.0 / 22.2 | 11.9 / 19.4 | 20.6 / 33.3 |
| 32 | 31.1 / 94.0 | 83.5 / 144.8 | 161.2 / 300.1 |
- Aurora delivers 2.0 to 4.5 times the messages per second of the RAW profile and 3.4 to 6.5 times those of the PRODUCTION profile; the median latency is 2.4 to 5.5 times lower than RAW and 4.2 to 7.9 times lower than PRODUCTION.
- From 16 to 32 connections throughput stays flat or drops for all profiles and latency roughly doubles: beyond that point, in the closed loop, adding connections no longer increases messages per second.
- At the 99th percentile Aurora stays below Mirth in every step except the clinical channel with one connection, where it is slightly above the RAW profile (18.5 vs 17.5 ms for ADT, 22.2 vs 19.4 ms for ORU).
02 · Eight hours
Eight hours of continuous load
Synthetic traffic, 100 msg/s
Synthetic traffic at 100 messages per second: clinical ADT channel at 80 msg/s over 8 connections and ORU at 20 msg/s over 4, three HTTP destinations each; 2,880,000 messages and 8,640,000 deliveries.
| Measure | ADT | ORU |
|---|---|---|
| Messages lost | 0 | 0 |
| ACK median / 95th / 99th | 4.1 / 6.9 / 9.9 ms | 4.7 / 7.9 / 11.1 ms |
| Maximum | 1,464 ms in the first minute, 211 ms afterwards | 1,357 ms in the first minute, 205 ms afterwards |
Average CPU 31.9% of one vCPU, maximum RSS 813 MiB, no Full GC; database between 6.64 and 8.53 GiB over the last four hours.
Real production channel, 2 reports per second
Real production channel at 2 reports per second: ORU^R01 with a 31 KB PDF, validation, remote SOAP signature, token and multipart upload to the document repository, update for repeated reports, MLLP notification to the departmental system and an ACK for every outcome. 57,600 reports per run, with 1,152 malformed and 224 injected faults answered with AE.
| Measure | STANDARD trace | DETAILED trace |
|---|---|---|
| Reports lost | 0 | 0 |
| ACK AA / AE | 56,224 / 1,376 | 56,224 / 1,376 |
| ACK median / 95th / 99th | 28.8 / 37.0 / 42.2 ms | 30.0 / 38.9 / 45.6 ms |
| Maximum | 1,647 ms in the first minute, 111 ms afterwards | 1,554 ms in the first minute, 142 ms afterwards |
| Database over the last four hours | 1.36 – 1.80 GiB | 6.40 – 8.50 GiB |
| Space per retained report | 50.6 KiB | 237.7 KiB |


Realistic reporting channel: 2.5.0 and 2.5.1
Three correlated channels (relay to the departmental system, reporting with remote PAdES signature, publication to a document repository with a queue of 5 per minute), 0.10 reports per second for eight hours with 1, 3 and 5 MiB PDFs, controlled errors and injected faults.
| Measure | Aurora 2.5.0 | Aurora 2.5.1 |
|---|---|---|
| Reports / signed / published | 2,880 / 2,704 / 2,700 | 2,880 / 2,704 / 2,700 |
| ORU report with signature, median / 95th / 99th | 437 / 1,712 / 1,819 ms | 445 / 1,749 / 1,836 ms |
| ORM orders | 28.8 / 36.4 / 42.0 ms | 28.6 / 36.0 / 42.0 ms |
| ADT patient messages | 30.8 / 39.3 / 58.7 ms | 30.8 / 38.9 / 50.4 ms |
| Average CPU / average heap | 6.2% / 926 MiB | 6.5% / 929 MiB |
| Full GC | 0 | 0 |
The report time includes synchronous conversion, signature and delivery and depends on the PDF size. In the 2.5.1 run a single ADT ACK took 5.2 s (1 of 2,880), with no garbage collector pause above 22 ms.
03 · September
Compared with the September edition
The bench has changed since September (host, VM operating system, Java 25, direct network, new measurement tools): absolute figures from the two editions are not directly comparable. On the real production channel we separated environment and code with four short 15-minute runs on the same bench: the Aurora 2.0 pre-release build used in the September tests, the 2.0.0 release build (9 September), 2.5.0 and 2.5.1.
| Real channel ACK, 15-minute runs | Aurora 2.0, September build | Aurora 2.0.0 | Aurora 2.5.0 | Aurora 2.5.1 |
|---|---|---|---|---|
| Median | 30.9 ms | 31.2 ms | 34.4 ms | 35.0 ms |
| 95th percentile | 51.0 ms | 52.8 ms | 61.2 ms | 64.9 ms |
| 99th percentile | 73.8 ms | 78.2 ms | 93.0 ms | 99.8 ms |

- The build used in September, which then measured 16.2 ms in the eight-hour run, measures 30.9 ms on the current bench (31.2 ms for the 2.0.0 release build): the distance from the first edition depends mostly on the environment.
- On the same bench 2.5.x needs about 3-4 ms more than the 2.0 builds at the median (10-13%); the largest part, about 2 ms, is in closing the message before the ACK, the rest over the other stages, with increases of at most 1 ms each.
- Space per report is in line with September for STANDARD (50.6 vs 48.8 KiB, September recalculated with the same method) and higher for DETAILED (237.7 vs 99.4 KiB): worth considering when sizing a DETAILED installation.
04 · Limitations
Stated limitations
- Mirth Connect “as installed”: 2 GiB heap versus 4 GiB for Aurora, no tuning, storage without pruning; channels rebuilt to be equivalent, with parsing, persistence and ACK handling native to each engine. With an optimised configuration Mirth's results may improve.
- Closed loop: each connection waits for the ACK before the next message, throughput depends on latency and latencies are not corrected for the waiting effect (coordinated omission).
- Short steps with a freshly started JVM: absolute values reflect the cold start, the comparison between engines does not.
- In the fastest steps the generator used with Aurora reaches about two thirds of one vCPU: Aurora's peaks may be partly limited by the bench.
- Downstream systems simulated over local HTTP without TLS (with a fixed 20 ms delay per call on the realistic channel); a single virtualised host: absolute values indicative, relative comparisons reliable.
Full sweep data: Show all 48 groups (engine, channel, connections)
| Engine | Channel | Conn. | msg/s | Median | 95th | 99th | CPU % | RSS MiB |
|---|---|---|---|---|---|---|---|---|
| Aurora 2.5.1 | Simple ADT | 1 | 482 | 1.79 | 2.89 | 6.71 | 30.0 | 536 |
| Aurora 2.5.1 | Simple ADT | 4 | 1,549 | 2.23 | 3.73 | 7.37 | 50.9 | 714 |
| Aurora 2.5.1 | Simple ADT | 16 | 2,941 | 4.47 | 9.56 | 15.42 | 99.0 | 927 |
| Aurora 2.5.1 | Simple ADT | 32 | 3,020 | 8.41 | 21.41 | 33.54 | 126.7 | 1,006 |
| Aurora 2.5.1 | Simple ORU | 1 | 348 | 2.36 | 3.80 | 7.44 | 31.6 | 533 |
| Aurora 2.5.1 | Simple ORU | 4 | 1,137 | 2.93 | 4.96 | 8.30 | 60.6 | 865 |
| Aurora 2.5.1 | Simple ORU | 16 | 1,773 | 7.49 | 14.80 | 21.51 | 124.7 | 1,104 |
| Aurora 2.5.1 | Simple ORU | 32 | 1,707 | 15.89 | 36.43 | 48.53 | 127.4 | 1,149 |
| Aurora 2.5.1 | Clinical ADT | 1 | 198 | 4.13 | 8.70 | 18.45 | 62.4 | 680 |
| Aurora 2.5.1 | Clinical ADT | 4 | 716 | 4.75 | 9.48 | 15.85 | 105.8 | 868 |
| Aurora 2.5.1 | Clinical ADT | 16 | 1,074 | 12.82 | 28.73 | 40.71 | 186.4 | 1,180 |
| Aurora 2.5.1 | Clinical ADT | 32 | 1,064 | 25.95 | 62.93 | 87.57 | 218.6 | 1,213 |
| Aurora 2.5.1 | Clinical ORU | 1 | 157 | 4.96 | 11.04 | 22.18 | 52.1 | 724 |
| Aurora 2.5.1 | Clinical ORU | 4 | 611 | 5.40 | 10.49 | 16.35 | 101.8 | 969 |
| Aurora 2.5.1 | Clinical ORU | 16 | 915 | 15.00 | 32.12 | 45.65 | 175.0 | 1,222 |
| Aurora 2.5.1 | Clinical ORU | 32 | 889 | 31.12 | 71.37 | 94.03 | 173.8 | 1,291 |
| Mirth RAW | Simple ADT | 1 | 139 | 6.70 | 9.82 | 13.03 | 33.0 | 590 |
| Mirth RAW | Simple ADT | 4 | 433 | 8.68 | 12.68 | 17.41 | 63.0 | 762 |
| Mirth RAW | Simple ADT | 16 | 811 | 18.46 | 29.36 | 36.71 | 108.1 | 830 |
| Mirth RAW | Simple ADT | 32 | 671 | 46.04 | 70.17 | 85.23 | 147.8 | 827 |
| Mirth RAW | Simple ORU | 1 | 109 | 8.43 | 11.86 | 15.08 | 31.8 | 726 |
| Mirth RAW | Simple ORU | 4 | 333 | 11.10 | 16.29 | 20.18 | 78.5 | 914 |
| Mirth RAW | Simple ORU | 16 | 620 | 24.37 | 37.20 | 45.61 | 140.7 | 830 |
| Mirth RAW | Simple ORU | 32 | 525 | 58.76 | 87.80 | 104.94 | 161.5 | 930 |
| Mirth RAW | Clinical ADT | 1 | 95 | 9.89 | 13.66 | 17.45 | 30.0 | 640 |
| Mirth RAW | Clinical ADT | 4 | 300 | 12.63 | 17.78 | 21.78 | 57.7 | 799 |
| Mirth RAW | Clinical ADT | 16 | 455 | 33.84 | 51.70 | 61.43 | 98.2 | 753 |
| Mirth RAW | Clinical ADT | 32 | 389 | 79.05 | 123.13 | 146.37 | 133.4 | 865 |
| Mirth RAW | Clinical ORU | 1 | 78 | 11.87 | 16.34 | 19.44 | 32.8 | 641 |
| Mirth RAW | Clinical ORU | 4 | 242 | 15.50 | 21.69 | 26.18 | 77.1 | 823 |
| Mirth RAW | Clinical ORU | 16 | 380 | 40.34 | 60.47 | 71.20 | 122.1 | 947 |
| Mirth RAW | Clinical ORU | 32 | 371 | 83.45 | 122.25 | 144.83 | 160.5 | 1,176 |
| Mirth PRODUCTION | Simple ADT | 1 | 86 | 11.06 | 15.46 | 18.69 | 24.1 | 745 |
| Mirth PRODUCTION | Simple ADT | 4 | 259 | 14.58 | 20.77 | 25.35 | 51.9 | 922 |
| Mirth PRODUCTION | Simple ADT | 16 | 484 | 31.03 | 48.36 | 60.48 | 89.6 | 878 |
| Mirth PRODUCTION | Simple ADT | 32 | 463 | 66.73 | 99.93 | 117.28 | 129.1 | 993 |
| Mirth PRODUCTION | Simple ORU | 1 | 70 | 13.32 | 18.45 | 21.97 | 27.3 | 593 |
| Mirth PRODUCTION | Simple ORU | 4 | 208 | 18.08 | 25.51 | 31.81 | 67.4 | 876 |
| Mirth PRODUCTION | Simple ORU | 16 | 388 | 39.18 | 58.62 | 71.00 | 103.8 | 929 |
| Mirth PRODUCTION | Simple ORU | 32 | 372 | 82.69 | 122.55 | 142.75 | 156.9 | 851 |
| Mirth PRODUCTION | Clinical ADT | 1 | 52 | 18.47 | 24.78 | 29.48 | 24.9 | 602 |
| Mirth PRODUCTION | Clinical ADT | 4 | 149 | 25.47 | 34.72 | 45.50 | 62.0 | 663 |
| Mirth PRODUCTION | Clinical ADT | 16 | 247 | 62.82 | 88.52 | 106.87 | 87.2 | 925 |
| Mirth PRODUCTION | Clinical ADT | 32 | 212 | 144.76 | 225.20 | 273.91 | 115.5 | 934 |
| Mirth PRODUCTION | Clinical ORU | 1 | 46 | 20.61 | 27.28 | 33.25 | 31.3 | 733 |
| Mirth PRODUCTION | Clinical ORU | 4 | 128 | 29.65 | 39.82 | 51.95 | 69.2 | 842 |
| Mirth PRODUCTION | Clinical ORU | 16 | 208 | 74.50 | 103.47 | 119.26 | 103.2 | 815 |
| Mirth PRODUCTION | Clinical ORU | 32 | 190 | 161.17 | 247.43 | 300.08 | 130.8 | 809 |
Environment: server with two AMD EPYC 7313 and 94 GiB RAM; Debian 13 VM with 8 vCPU and PostgreSQL 16.15 for the system under test; generators and simulated destinations on a separate Rocky Linux 9.7 VM. Aurora 2.5.1 on Temurin 25.0.5, Mirth Connect 4.5.2 on Temurin 17. Aurora's system database is PostgreSQL 14 or later. Internal tests run by TECHEMV, without the involvement of independent third parties, using synthetic data only; raw data, scripts and channels available on request.
The previous edition (September 2026, Aurora 2.0) remains available: September report (PDF, Italian).
Mirth Connect is a trademark of NextGen Healthcare, Inc., which did not take part in these tests and has not endorsed them; the name is used only to identify the product compared. Aurora Integration Engine is a product of TECHEMV SRL.
Evaluating an integration engine, or moving off Mirth Connect?
Bring your projects: the demo runs on your own cases.