User Tools

Site Tools


cluster:132

Warning: Undefined array key -1 in /usr/share/dokuwiki/inc/html.php on line 1458

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cluster:132 [2014/08/08 14:49]
hmeij
cluster:132 [2014/08/11 10:08] (current)
hmeij [Tests]
Line 62: Line 62:
 </code> </code>
  
-Here are the steps for cloning v1 to v5. You'll need ''guestfish' part of the libguestfs tools allowing you to edit content inside the block level file.  Very nifty.+Here are the steps for cloning v1 to v5. You'll need ''guestfish'' part of the libguestfs tools allowing you to edit content inside the block level file.  Very nifty.
  
   * yum install libguestfs-tools-c   * yum install libguestfs-tools-c
Line 68: Line 68:
 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 '05' (make it unique). Name becomes v5 from v1 and we'll similarly adjust the block device location/filename. Then we define this as domain v5. 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 '05' (make it unique). Name becomes v5 from v1 and we'll similarly adjust the block device location/filename. Then we define this as domain v5.
  
-Launch ''guestfish' and make the same edits to Mac Address in files listed below. Then boot the vm.+Launch ''guestfish'' and make the same edits to Mac Address in files listed below. Then boot the vm.
  
 <code> <code>
Line 109: Line 109:
  
  
-Number of jobs running (Melt Lammps LJ problem, 10000 steps with 32000 atoms) ^^^^^^^^^ +^ Melt Lammps LJ problem, 10000 steps with 32000 atoms Loop Times (secs) ^^^^^^^^^ 
-|  2  |  4  |  6  |  8  |  10  |  12  |  14  |  16  |    |+|  2  |  4  |  6  |  8  |  10  |  12  |  14  |  16  |  nr of jobs  |
 |  556  |  560  |  588  |  625  |  760  |  936  |  1122    1300  |    | |  556  |  560  |  588  |  625  |  760  |  936  |  1122    1300  |    |
 |  (linear)  ||||  781  |  938  |  1094  |  1250  |    |  |  (linear)  ||||  781  |  938  |  1094  |  1250  |    | 
Line 117: Line 117:
  
  
-16 VMs running in queue ''testvm''+16 VMs running in queue ''testvm'' on dual quad core PE2950 (8 cores, 16 GB ram)
  
   * First ran on n35 (32 core node under hyperthreading will full load) with an average loop time 726 secs.   * First ran on n35 (32 core node under hyperthreading will full load) with an average loop time 726 secs.
Line 131: Line 131:
 But we learned Xen and KVM setups, and But we learned Xen and KVM setups, and
  
-  - We can now support a heterogeous environment if we wanted (Suse, Scientific Linux, Windows (eh, what?)) +  - We can now support a heterogeneous environment if we wanted (Suse, Scientific Linux, Windows (eh, what?)) 
-  - Using a KVM environment up to the number of cores on a box+  - 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)   - 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" problem, see [[cluster:133|high core count/low memory footprint]]   - Still, not an answer for my "high core count/low memory footprint" problem, see [[cluster:133|high core count/low memory footprint]]
cluster/132.1407523766.txt.gz · Last modified: 2014/08/08 14:49 by hmeij