You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/measuring/measurement-cluster.md
+37Lines changed: 37 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,6 +136,43 @@ We have the following machines available for running measurements in our cluster
136
136
+ Metrics Provider for Machine Power: [IPMI]({{< relref "metric-providers/psu-energy-ac-ipmi-machine" >}})
137
137
+ Special: **SoftAWERE compatible**
138
138
139
+
## How to choose
140
+
141
+
### Profiling Machines
142
+
143
+
These machines are configured to be best representative of an off-the-shelf energy configuration.
144
+
145
+
This means:
146
+
147
+
- CPU Power Hungry but user friendly features like TurboBoost are on
148
+
- Low-Load multi-tasking optimizing features like HyperThreading are turned on
149
+
- Frequency Limits and C-State-Limits which typically make workloads more reproducible
150
+
for all tenants (and thus are typically activated in the cloud) are not set.
151
+
152
+
You should choose these kind of machines to get an idea of how much actual energy an application might be using on an off-the-shelf installation. This energy value is thus very representative for desktop, home user or shared hosting situations.
153
+
154
+
It is also very good to show how good your software can leverage sleep states or how good it mitigates wakeups and thus highlight it's power saving features.
155
+
156
+
### Benchmarking Machines
157
+
158
+
These machines are configured to increase reproducability by turning off some variance introducing features but still allow a reasonable difference between low load and high load scenarios on the machine
159
+
160
+
- Strongly non linear features like TurboBoost and DVFS are turned off
161
+
- Frequency is limited to only the base clock rate of the CPU
162
+
- C-States are limited to C1 reduce latency from wakeups, but still let CPU not stay in a spin-lock
163
+
164
+
You should choose these machine types if you want have strongly reproducible runs that are not impacted by home user configurations like power saving features. This also corresponds to configurations of most cloud vendors and thus are more represeantative of a cloud workload.
165
+
166
+
Also consider to choose a machine that has the metric providers with sampling rates apt for the effect you want to capture. See [Sampling Rate Best Practices]({{< relref "best-practices/#3-sampling-rate">}})for more details.
167
+
168
+
Drawbacks are that it cannot show the full potential how good an application leverages power saving features.
169
+
170
+
### HPC Benchmarking
171
+
172
+
These machines are configured for extreme compute scenarios effectively turning off all latency introducing features completely. Optionally some compute power improvements features like Pre-Fetching can be enabled
173
+
174
+
HPC Benchmarking machines are only available in the enterprise plan as the must be configured to the users request. If you plan to make HPC Benchmarking on our cluster please contact us and send us your desired CPU, DRAM and GPU configuration and power capping settings.
175
+
139
176
## Setting up your own measurement cluster
140
177
141
178
Please refer to the page [Installation of a Cluster]({{< relref "/docs/cluster/installation" >}})
0 commit comments