D2 3 Computing e-Infrastructure cost calculations and business _models_vam1-final
D2 3 Computing e-Infrastructure cost calculations and business _models_vam1-final
D2 3 Computing e-Infrastructure cost calculations and business _models_vam1-final
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
e-‐FISCAL: www.efiscal.eu <br />
EC Contract Number: 283449 <br />
4.4.2 Performance adjusted comparison (based on benchmarking) –<br />
Amazon<br />
We have also compared the prices of Amazon with the <strong>cost</strong>s of the Basic case of e-‐FISCSAL after incorporating in <br />
the analysis the results of the benchmarking exercise for both HTC <strong>and</strong> HPC (details about the benchmarking <br />
exercise are found in Appendix 7.7). <br />
The main findings of the benchmarking exercise as well as the way they had been incorporated in the price <br />
comparisons are discussed below <br />
HTC vs. Cloud benchmarking <br />
The HTC vs. Cloud benchmarking effort focused on the comparison of the relevant Amazon EC2 instance types <br />
versus HTC instances. It is worth clarifying here that the classification of the EC2 instances as an HPC or HTC <br />
instance is done based on the Amazon specification for various instances types. The following Table 11 <br />
summarises the results of the benchmarks with various different instance <strong>and</strong> processor types: <br />
Benchmark & Instance <br />
Type <br />
HEPSPEC06 + M1 Medium <br />
instance + S<strong>and</strong>y Bridge <br />
HEPSPEC06 + M1 Medium <br />
instance + Opteron <br />
HEPSPEC06 + M1 Large <br />
instance + S<strong>and</strong>y Bridge <br />
HEPSPEC06 + M1 Large <br />
instance + Opteron <br />
HEPSPEC06 + M1 X-‐Large <br />
instance + S<strong>and</strong>y Bridge <br />
HEPSPEC06 + M3 X-‐Large <br />
instance + S<strong>and</strong>y Bridge <br />
HEPSPEC06 + M3 Double <br />
X-‐Large instance + S<strong>and</strong>y <br />
Bridge <br />
Average EC2 <br />
Performance impact in % <br />
-‐48 <br />
-‐18 <br />
-‐59 <br />
-‐31 <br />
-‐46 <br />
-‐43 <br />
-‐38 <br />
Ranges for the EC2 <br />
performance impact in % <br />
-‐3 to -‐58 <br />
-‐4 to -‐48 <br />
-‐9 to -‐57 <br />
-‐9 to -‐49 <br />
-‐8 to -‐56 <br />
-‐18 to -‐55 <br />
-‐9 to -‐ 55 <br />
Table 11: EC2 M1 (M, L, XL) <strong>and</strong> M3 (XL, Double XL) VS. HTC instances (Intel+AMD) @ INFN<br />
The HEPSEPC06 benchmark is used to compare the Cloud vs. HTC infrastructure. In order to compare the effect of <br />
distinct characteristics (i.e. virtualization, multi-‐tenancy, resource over-‐subscription) <strong>and</strong> possible variations within <br />
the Cloud infrastructure, HTC instances <strong>and</strong> benchmarking environment were configured in multiple settings <strong>and</strong> <br />
HEPSPEC06 was executed on each setting. The idea for each individual setting was to obtain the results for <br />
performance variations while taking into account the best-‐case <strong>and</strong> worst-‐case scenarios. The best-‐case scenario <br />
here could reflect the situation with many of the existing HTC centres (i.e. no virtualisation or bare-‐metal) or <br />
virtualization with minimum possible workload. On the contrary, the worst-‐case would include the fully loaded <br />
machine with “n” number of virtual machines <strong>and</strong> all running HEPSPEC06 or even the case when the available <br />
resources (e.g. memory) are over-‐subscribed among the virtual machines. <br />
e-‐FISCAL : Financial Study for Sustainable <strong>Computing</strong> e-‐<strong>Infrastructure</strong>s <br />
Deliverable <strong>D2</strong>.3 – <strong>Computing</strong> e-‐<strong>Infrastructure</strong>s <strong>cost</strong> estimation <strong>and</strong> analysis – Pricing <strong>and</strong> <br />
Business <strong>models</strong> <br />
57
Change language