cluster:132
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cluster:132 [2014/08/08 12:06] hmeij |
cluster:132 [2014/08/11 10:08] (current) hmeij [Tests] |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| - | Ah, I'm simply going to CentOS7 | + | Ah, I'm simply going to CentOS-7 |
| * [[http:// | * [[http:// | ||
| Line 37: | Line 37: | ||
| ==== KVM ==== | ==== KVM ==== | ||
| - | KVM is hardware level virtualization as opposed to my previous meanderings into the world of software level virtualization (Xen). | + | KVM is hardware level virtualization as opposed to my previous meanderings into the world of software level virtualization (Xen [[cluster: |
| * Followed the primary setup on this page | * Followed the primary setup on this page | ||
| Line 48: | Line 48: | ||
| * http:// | * http:// | ||
| - | First I build my v1 clone the way I wanted it from ISO and then customized it manually (/ | + | First I create my v1 clone with virt-install then build my v1 clone the way I wanted it and then customized it manually (/ |
| < | < | ||
| Line 62: | Line 62: | ||
| </ | </ | ||
| - | Here are the steps for cloning v1 to v5. You'll need '' | + | Here are the steps for cloning v1 to v5. You'll need '' |
| * yum install libguestfs-tools-c | * yum install libguestfs-tools-c | ||
| - | Next we'll create the v5.img block device, dump the v1 config into v5.xml and then edit that file. UUID and Mac Address we'll edit and the last 2 characters we change to ' | + | Next we'll create the v5.img block device, dump the v1 config into v5.xml and then edit that file. UUID and Mac Address we'll edit and the last 2 characters we change to ' |
| - | Launch '' | + | Launch '' |
| < | < | ||
| Line 95: | Line 95: | ||
| >< | >< | ||
| >< | >< | ||
| - | (for nics comment out any UUID lines, change | + | (for nics comment out any UUID lines, change |
| >< | >< | ||
| (change hardware address) | (change hardware address) | ||
| Line 107: | Line 107: | ||
| ==== Tests ==== | ==== Tests ==== | ||
| - | < | ||
| - | 2 | ||
| - | 556 560 588 625 760 936 1122 1300 | ||
| - | | ||
| - | | ||
| - | < | + | ^ Melt Lammps LJ problem, 10000 steps with 32000 atoms Loop Times (secs) ^^^^^^^^^ |
| + | | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16 | nr of jobs | | ||
| + | | 556 | 560 | 588 | 625 | 760 | 936 | 1122 | ||
| + | | (linear) | ||
| + | | (n35:load 32) |||| 726 | | | | | | ||
| + | | (hyperthreading) | ||
| + | |||
| + | |||
| + | 16 VMs running in queue '' | ||
| + | |||
| + | * First ran on n35 (32 core node under hyperthreading will full load) with an average loop time 726 secs. | ||
| + | * As I submit jobs to the VMs they perform well up to 8 jobs (one job per core; dual quad core node). | ||
| + | * That is with the KVM overhead | ||
| + | * Assuming a linear penalty for over committing, 16 jobs is expected to take Loop times of 1250 secs. | ||
| + | * However after 10 jobs we're surpassing that penalty threshold | ||
| + | * And then I was to turn on Hyperthreading creating 16 logical cores | ||
| + | * To my dismay this chipset does not support that, bummer! | ||
| + | * Was expecting to gain some performance back ... | ||
| + | * Maybe try on newer hardware when idle ... | ||
| + | |||
| + | But we learned Xen and KVM setups, and | ||
| + | |||
| + | - We can now support a heterogeneous environment if we wanted (Suse, Scientific Linux, Windows (eh, what?)) | ||
| + | - Use a KVM environment up to the number of cores on a box without penalty | ||
| + | - And change the mix of nodes if needed (more/less cores per node, memory size etc) | ||
| + | - Still, not an answer for my "high core count/low memory footprint" | ||
| \\ | \\ | ||
cluster/132.1407514010.txt.gz · Last modified: 2014/08/08 12:06 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
