Il 18/11/20 15:15, Jason Simms ha scritto:
> Use of uninitialized value $hash{"2"} in division (/) at /bin/seff line
> 108, line 602.
> Use of uninitialized value $hash{"2"} in division (/) at /bin/seff line
> 108, line 602.
Seems some setups report data in a different format, hence the
uninitia
Dear Peter,
Thanks for your response. Yes, I am running ProctrackType=proctrack/cgroup
The behavior that I was seeing with the default seff, and that Diego saw as
well, was simply that seff was not reporting really any information for a
given job. I'm glad it's working for you, but it doesn't for
On Wed, 18 Nov 2020 09:15:59 -0500
Jason Simms wrote:
> Dear Diego,
>
> A while back, I attempted to make some edits locally to see whether I
> could produce "better" results. Here is a comparison of the output of
> your latest version, and then mine:
I'm not sure what bug or behavior you're se
Dear Diego,
A while back, I attempted to make some edits locally to see whether I could
produce "better" results. Here is a comparison of the output of your latest
version, and then mine:
[root@hpc bin]# seff 24567
Use of uninitialized value $hash{"2"} in division (/) at /bin/seff line
108, line
Il 09/11/20 12:53, Diego Zuccato ha scritto:
> Seems my corrections actually work only for single-node jobs.
> In case of multi-node jobs, it only considers the memory used on one
> node, hence understimates the real efficiency.
> Someone more knowledgeable than me can spot the error?Seems I manag
Il 15/09/20 10:14, Diego Zuccato ha scritto:
Seems my corrections actually work only for single-node jobs.
In case of multi-node jobs, it only considers the memory used on one
node, hence understimates the real efficiency.
Someone more knowledgeable than me can spot the error?
TIA!
> I'm neither
Il 10/09/20 22:19, Jason Simms ha scritto:
> I've found that when I run seff, it fails to report calculated values, e.g.:
I didn't know seff. Quite interesting. Same problem detected.
I'm neither Perl nor Slurm expert so I'm quite sure there's a better way
to do it, but I "fixed" it by changing at
Hello all,
I've found that when I run seff, it fails to report calculated values, e.g.:
Nodes: 1
Cores per node: 20
CPU Utilized: 00:00:00
CPU Efficiency: 0.00% of 1-11:49:40 core-walltime
Job Wall-clock time: 01:47:29
Memory Utilized: 0.00 MB (estimated maximum)
Memory Efficiency: 0.00% of 180.0
