On Thursday, 30 November 2017 9:58:08 PM AEDT Markus Köberl wrote:
> I also saw the wrong Sockets, CPU and Threads. I did not recognize the wrong
> values for RAM. Therefore I did define Sockets, CoresPerSocket,
> ThreadsPerCore and RealMemory.
You can run "slurmd -C" to get it to tell you the co
On Tuesday, 21 November 2017 16:38:48 CET Ing. Gonzalo E. Arroyo wrote:
> I have a problem detecting RAM and Arch (maybe some more), check this...
>
> NodeName=fisesta-21-3 Arch=x86_64 CoresPerSocket=1
>CPUAlloc=0 CPUErr=0 CPUTot=2 CPULoad=0.01
>AvailableFeatures=rack-21,2CPUs
>ActiveF
I have a problem detecting RAM and Arch (maybe some more), check this...
NodeName=fisesta-21-3 Arch=x86_64 CoresPerSocket=1
CPUAlloc=0 CPUErr=0 CPUTot=2 CPULoad=0.01
AvailableFeatures=rack-21,2CPUs
ActiveFeatures=rack-21,2CPUs
Gres=gpu:1
NodeAddr=10.1.21.3 NodeHostName=fisesta-21-3
On Tuesday, 21 November 2017 10:26:53 CET Merlin Hartley wrote:
> Could you give us your submission command?
> It may be that you are requesting the wrong partition - i.e. relying on the
> default partition selection… try with “--partition cpu”
I run the following commands:
srun --gres=gpu --mem-
Could you give us your submission command?
It may be that you are requesting the wrong partition - i.e. relying on the
default partition selection…
try with “--partition cpu”
M
--
Merlin Hartley
Computer Officer
MRC Mitochondrial Biology Unit
Cambridge, CB2 0XY
United Kingdom
> On 21 Nov 20
On Friday, 3 November 2017 10:12:32 CET Merlin Hartley wrote:
> They would need to have different NodeNames - but the same NodeAddr for
> example:
>
> NodeName=fisesta-21-3 NodeAddr=10.1.21.3 CPUs=6 Weight=20485797
> Feature=rack-21,6CPUs NodeName=fisesta-21-3-gpu NodeAddr=10.1.21.3 CPUs=2
> Weigh
