cluster:125
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
cluster:125 [2014/02/19 09:53] hmeij |
cluster:125 [2014/02/26 15:30] hmeij |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| \\ | \\ | ||
| **[[cluster: | **[[cluster: | ||
| + | |||
| + | Done! | ||
| + | --- // | ||
| ==== Dell Racks Power Off ==== | ==== Dell Racks Power Off ==== | ||
| Line 32: | Line 35: | ||
| #BSUB -R " | #BSUB -R " | ||
| </ | </ | ||
| + | |||
| + | * How do I find out how much memory I'm using? ssh node_name top -u your_name -b -n 1 | ||
| Gaussian: | Gaussian: | ||
| Line 72: | Line 77: | ||
| * if there is no ‘sharing’ required the hyper-threaded node performs the same (that is the operating systems presents 16 cores but only up to 8 jobs are allowed to run, lets say by limiting the JL/H parameter of the queue) | * if there is no ‘sharing’ required the hyper-threaded node performs the same (that is the operating systems presents 16 cores but only up to 8 jobs are allowed to run, lets say by limiting the JL/H parameter of the queue) | ||
| - | | + | * if there is ‘sharing’ jobs take a 44% speed penalty, however more of them can run, twice as many |
| So it appears that we could turn hyperthreading on and despite the nodes presenting 16 cores we could limit the number of jobs to 8 until the need arises to run many small jobs and then reset the limit to 16. | So it appears that we could turn hyperthreading on and despite the nodes presenting 16 cores we could limit the number of jobs to 8 until the need arises to run many small jobs and then reset the limit to 16. | ||
cluster/125.txt · Last modified: 2014/02/26 15:32 by hmeij
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
