here - Stefan-Marr.de

8.5. Assessment of Performance Characteristics
Runtime Ratio, normalized to
RoarVM+OMOP (full), lower is better
1.08
1.06
1.04
1.02
1.00
0.98
0.96
RoarVM+OMOP (full)
RoarVM+OMOP (opt)
Binary Trees
Fannkuch
Fasta
NBody
Slopstone
Figure 8.9.: Customization Constant, Enforced Execution: Comparing
RoarVM+OMOP (opt) with RoarVM+OMOP (full) to assess the inherent
overhead of checking the customization constant during fully enforced execution.
The benchmarks utilize the OMOP but all intercession handlers implement
standard semantics. The results show that the additional check leads to an
average runtime overhead of 3%.
Fig. 8.10 depicts the results in the form of beanplots. The microbenchmarks
show a significant benefit of avoiding reification for uncustomized intercession
handlers. Especially the microbenchmarks for message sends for LRSTM
show the benefit. Since the LRSTM system does not require message sends to
be customized, they are between 2x and 2.5x faster, depending on the number
of arguments.
The kernel benchmarks on the other hand show more realistically what
the benefit of this optimization could be for application code. The average
measured gain is 5%. For the Fannkuch benchmark on AmbientTalkST, the
overhead of the additional check is higher and performance is not improved,
because all intercession handlers have to be triggered. Thus, this benchmark
shows a slowdown of 2%. The average 5% gain for the given benchmarks and
concurrency models is rather modest. For other concurrency models, such
as Clojure actors, higher benefits can be expected, because for instance the
reading of object fields does not need to be reified.
225