This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
cluster:127 [2014/04/07 13:46] hmeij |
cluster:127 [2014/04/07 13:48] (current) hmeij |
||
---|---|---|---|
Line 48: | Line 48: | ||
Then launch '' | Then launch '' | ||
- | Build a base clone and install what you need (like the Lava scheduler files). Give it a static IP via / | + | Build a base clone and install what you need (like the Lava scheduler files). Give it a static IP via / |
Now you build a script to clone and post prep new clones build from it. | Now you build a script to clone and post prep new clones build from it. | ||
Line 117: | Line 117: | ||
The 6vms with 32vcpus finished work after 22 hours. That would imply one of these nodes could run say 20 VMs with 20x32=640 job slots. And we have 20 servers (12,800 job slots) that could be virtualized but there is no performance gain. Those servers will finish the 12,800 jobs in the same time not being virtualized. Too bad really. | The 6vms with 32vcpus finished work after 22 hours. That would imply one of these nodes could run say 20 VMs with 20x32=640 job slots. And we have 20 servers (12,800 job slots) that could be virtualized but there is no performance gain. Those servers will finish the 12,800 jobs in the same time not being virtualized. Too bad really. | ||
- | Following that thought, we could virtualize (KVM at hardware level) one of the new Asus servers; at 256 gb of memory this would yield 8,192 job slots for one node 128 mb per vcpu). | + | Following that thought, we could virtualize (KVM at hardware level) one of the new Asus servers; at 256 gb of memory this would yield 8,192 job slots for one node 128 mb per vcpu). That might be an option. |
\\ | \\ |