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
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
e-‐FISCAL: www.efiscal.eu <br />
EC Contract Number: 283449 <br />
Amazon EC2 <br />
HTC resource at INFN <br />
Compute <br />
Nodes <br />
Medium: 2 ECU <br />
Large: 4 ECU <br />
XL: 8 ECU <br />
M3 XL: 13 ECU <br />
M3 2 XL: 26 ECU <br />
1 ECU = 1.0-‐1.2 GHz of <br />
Intel Xeon or AMD <br />
Opteron <br />
OS SL6.2, 64-‐bit platform SL6.2, 64-‐bit platform <br />
Memory <br />
Hyper-‐<br />
Threading <br />
3.75 GB, 7.5 GB <strong>and</strong> 15 <br />
GB <br />
Enabled <br />
Compilers GCC GCC <br />
-‐ Intel(R) Xeon(R) CPU E5-‐2660 @ 2.2 GHz, 2 X 8 cores, 64 <br />
GB memory <br />
-‐ AMD Opteron 6272 (aka Interlagos) @ 2.1 GHz, 2 X 16 <br />
cores <br />
• M instance Single-‐core VM <br />
• L instance Dual-‐core VM <br />
• XL Instance Quad-‐core VM <br />
• M3 XL Instance Quad-‐core VM <br />
• M3 Double XL Instance Eight Core VM <br />
64 GB for both Intel <strong>and</strong> AMD <br />
Enabled (for Intel) ~ 32 logical cores <br />
Table 28 – Benchmarking system specification <br />
HTC Benchmarking – Settings <strong>and</strong> Results <br />
This section will cover the details on the benchmarking settings that are deployed to compare the in-‐house <strong>and</strong> <br />
Amazon EC2 instances. As a first step, the following sub-‐section will detail the various benchmark settings. <br />
Benchmark Settings <br />
The rationale behind the following benchmark settings is to try to simulate the public Cloud characteristics i.e. <br />
virtualization, multi-‐tenancy, resource over-‐subscription <strong>and</strong> load variations. As there is no other simple way to <br />
study the effect of these distinct Cloud characteristics within the Cloud computing infrastructures. The following <br />
benchmark settings are adopted: <br />
• HEPSPEC6 on Bare-‐metal vs. EC2: The HEPSPEC06 results on bare-‐metal vs. EC2 demonstrates the <br />
performance impact while running applications on non-‐virtualised infrastructure vs. EC2 virtualised <strong>and</strong> <br />
multi-‐tenant infrastructure. <br />
• HEPSPEC6 on 1 virtual machine vs. EC2: The HEPSPEC06 result on 1 virtual machine compared against the <br />
bare-‐metal case yields the virtualization over-‐head. However, it is unlikely to have a comparable case in a <br />
commercial cloud setting where there will be only one virtual machine running in the whole <br />
infrastructure. <br />
• HEPSPEC6 on n virtual machines with minimal workload vs. EC2: In order to simulate the effect of multi-tenancy<br />
physical machine was loaded with the maximum number of possible virtual machines it could <br />
accommodate without any resource oversubscription. And then the HEPSPEC06 results are compared for <br />
both in-‐house <strong>and</strong> EC2 Cloud instances. This test case simulates the effect of multi-‐tenancy with minimal <br />
workload. <br />
• HEPSPEC6 on n virtual machines with maximum workload vs. EC2: To simulate the effect of worst-‐case <br />
scenario, all machines within the multi-‐tenant in-‐house infrastructure are fully loaded with HEPSEPC06 <br />
<strong>and</strong> then results are compared with the EC2 instances. <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 />
97
Change language