here - Stefan-Marr.de

8. Evaluation: Performance
1.10
1.08
1.06
1.04
1.02
1.00
0.98
0.96
Binary Trees
Chameneos
Fannkuch
Fasta
NBody
Compiler
Slopstone
Smopstone
Runtime Ratio, normalized to
RoarVM+OMOP (full), lower is better
RoarVM+OMOP (full)
RoarVM+OMOP (opt)
Figure 8.8.: Customization Constant, Unenforced Execution: Comparing
RoarVM+OMOP (opt) with RoarVM+OMOP (full) to assess the inherent
overhead of customization constant changes. The benchmarks do not utilize
the OMOP, and thus, they expose that this check leads to an average runtime
overhead of 1%. Since the impact is varying for the benchmarks and in some
cases even reduces the runtime, the overall conclusion is that changes that
introduce the check of the customization constant have a negligible impact on
unenforced execution.
Overhead during Enforced Execution Fig. 8.9 25 shows the results for the
enforced execution of the kernel benchmarks. Here the overhead comes from
the additional check, which only confirms that all intercession handlers have
to be used. The slowdown ranges from 2% to 4%, and average slowdown is
3%. Thus, there is a measurable, but minor overhead.
Speedup for AmbientTalkST and LRSTM Finally, the performance gains of
using the customization constant for the AmbientTalkST and LRSTM benchmarks
are measured. AmbientTalkST customizes all intercession handlers and
should therefore show no gain or a minimal overhead for using the customization
constant. LRSTM on the other hand only customizes state access while
message sends are not customized. Consequently, it is expected to benefit
significantly from avoiding overhead on every message send.
25 The beanplot library of R forced a linear scale for this graph.
224