05.08.2014 Views

here - Stefan-Marr.de

here - Stefan-Marr.de

here - Stefan-Marr.de

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

B<br />

A P P E N D I X : P E R F O R M A N C E E VA L U AT I O N<br />

This appendix characterizes the used benchmarks and gives the configuration<br />

informations used for the benchmarks <strong>de</strong>scribed in Chapter 8.<br />

B.1. Benchmark Characterizations<br />

This section gives an overview over the different benchmarks used in this<br />

evaluation. This characterization is meant to facilitate the discussion and interpretation<br />

of our benchmark results in Chapter 8.<br />

We categorize the benchmarks in microbenchmarks and kernel benchmarks to<br />

distinguish their general characteristics and scope. None of these benchmarks<br />

qualifies as a real world application benchmark, as for instance <strong>de</strong>fined by the<br />

DaCapo benchmarks [Blackburn et al., 2006].<br />

The benchmarks used in this evaluation have either been implemented<br />

specifically for our experiments or are <strong>de</strong>rived from commonly used benchmarks.<br />

While the microbenchmarks are <strong>de</strong>signed to measure a single aspect<br />

of the implementation, the kernel benchmarks are meant to represent a number<br />

of typical performance sensitive work loads that can be found embed<strong>de</strong>d<br />

in applications.<br />

The remain<strong>de</strong>r of this section discusses the used benchmarks, their characteristics,<br />

and our expectation of their behavior. Furthermore, we <strong>de</strong>scribe the<br />

adaptations to use them in the context of LRSTM and AmbientTalkST, as well<br />

as our expectation of how the benchmark behaves on top of i<strong>de</strong>al implementations<br />

of these systems.<br />

261

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!