Skip to content

4.0 Or Newer

Environment

Our test machine has the following setup:

  • Operating System: Microsoft Windows 10 Enterprise N
  • Processor: Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz, 3504 Mhz, 4 Core(s), 8 Logical Processor(s)
  • Memory: 64 GB

Any results marked with an asterisk (*) are done with EAP(X) models, starting with 4.0.0 we will focus our performance testing on QEA(X) models.

Test results

Small Model

LT Version 1) Loading models 2) Premerge calculation 3) Writing merge file Max RAM usage
4.1.0 3s 0s 1s 319 MB
4.0.0 2s 0s 1s 756 MB
3.3.1* 3s 0s 0s 901 MB
3.3.0* 3s 0s 0s 740 MB

Medium Model

LT Version 1) Loading models 2) Premerge calculation 3) Writing merge file Max RAM usage
4.1.0 1m8s 7s 20s 5.634 MB
4.0.0 1m1s 6s 21s 6.546 MB
3.3.1* 1m0s 7s 13s 6.867 MB
3.3.0* 1m4s 8s 12s 6.364 MB

Large Model

LT Version 1) Loading models 2) Premerge calculation 3) Writing merge file Max RAM usage
4.1.0 2m0s 3m6s 18m2s 13.998 MB
4.0.0 2m11s 3m10s 18m54s 12.867 MB
3.3.1* 2m14s 3m38s 17m31s 14.924 MB
3.3.0* 2m14s 3m47s 17m41s 14.827 MB

EAExample

LT Version 1) Loading models 2) Premerge calculation 3) Writing merge file Max RAM usage
4.1.0 8s 11s 1m51s 902 MB
4.0.0 5s 8s 1m56s 2.405 MB
3.3.1* 9s 8s 2m19s 1.886 MB
3.3.0* 8s 9s 2m23s 1.563 MB

Tagged Value Model

LT Version 1) Loading models 2) Premerge calculation 3) Writing merge file Max RAM usage
4.1.0 1m7s 11s 3m10s 4.444 MB
4.0.0 1m5s 12s 3m16 6.005 MB
3.3.1* 1m7s 18s 2m53s 7.810 MB
3.3.0* 1m11s 14s 3m5ss 7.799 MB

TV Model (Triple Size)

LT Version 1) Loading models 2) Premerge calculation 3) Writing merge file Max RAM usage
4.1.0 3m4s 33s 11m10s 12.955 MB
4.0.0 3m12s 36s 11m50s 11.482 MB
3.3.1* 3m28s 41s 11m53s 18.702 MB
3.3.0* 3m13s 41s 11m43s 19.500 MB

Remarks

The new test machine consumes significantly more memory for the "Large Model" and the "TV Model (Triple Size)" - even with LemonTree versions which have completed the same merges on the old test hardware with significantly less memory usage. We currently assume that this is because the garbage collector isn't triggered as often on this machine because of excess available RAM - or, in layman's terms - if the RAM is available, LemonTree is going to use it. This speeds up the merge in total. However, we don't have any insight yet how much of the performance gain is due to the change in processing power, and how much is due to the additional RAM. This circumstance is still under investigation.