-
Notifications
You must be signed in to change notification settings - Fork 1
'A'* stands for a set of application models -- any one application model of this set represents a specific class of applications which exhibit similar decomposition, and similar mapping of semantics to workload components, and thus similar execution structure. For example, the set 'bag of independent homogenous tasks' exhibits a well defineable set of execution properties, but can ultimately represent a large number of application instances (which are ultimately defined by their semantic load). A* modeling can be used and parametrized to create Synthetic Applications, i.e. application descriptions which truthfully represent the execution properties of the respective application class, without actually performing the application semantics.
Application Skeletons provide similar properties, and also faithfully recreate the execution properties for a certain (parametrizable) sets of applications. The main difference is that skeletons are derived from actual applications -- and thus possibly more truthful, while the creation of Synthetic Applications is model driven -- and thus possibly easier to reason about. More specifically, that model driven approach should allow (via model parametrization) to reason about (static and dynamic) infrastructure properties, and to adapt application properties, such as coordination and communication models, or application decomposition, accordingly.
- covers different areas: skeletons, app frameworks, gateways, workflows, etc.
- skeletons: generator of artificial workloads according to some reciepie
- frameworks: translates app semantics to workloads
- synthetic applications: 'artificial' workloads
- system workloads: derivation of workloads, adds resource consumption details
- Analytical Application Models
- Application Simulation
- Application Emulation
- Experiments
- spans from A* to over 4' to real workload on a real infrastructure
- descriptions need an underlying model