Am 15.12.2022 um 08:23 schrieb Bjørn-Helge Mevik:
Marcus Wagner writes:
it it important to know, that the json output seems to be broken.
First of all, it does not (compared to the normal output) obey to the truncate
option -T.
But more important, I saw a job, where in a "day output" (-S
Marcus Wagner writes:
> it it important to know, that the json output seems to be broken.
>
> First of all, it does not (compared to the normal output) obey to the
> truncate option -T.
> But more important, I saw a job, where in a "day output" (-S -E
> ) no steps were recorded.
> Using sacct
Hi Bjørn-Helge,
it it important to know, that the json output seems to be broken.
First of all, it does not (compared to the normal output) obey to the truncate
option -T.
But more important, I saw a job, where in a "day output" (-S -E
) no steps were recorded.
Using sacct -j --json instead
Hi Paul,
as Slurm uses hwloc, I was looking into these tools a little bit deeper.
Using your script, I saw e.g. the following output on one node:
=== 31495434
CPU_IDs=21-23,25
21-23,25
=== 31495433
CPU_IDs=16-18,20
10-11,15,17
=== 31487399
CPU_IDs=15
9
That does not match your schemes and on
The seff utility (in slurm-contribs) also gives good summary info.
You can also you --parsable to make things more managable.
-Paul Edmon-
On 12/14/22 3:41 PM, Ross Dickson wrote:
I wrote a simple Python script to transpose the output of sacct from a
row into a column. See if it meets your
I wrote a simple Python script to transpose the output of sacct from a row
into a column. See if it meets your needs.
https://github.com/ComputeCanada/slurm_utils/blob/master/sacct-all.py
- Ross Dickson
Dalhousie University / ACENET / Digital Research Alliance of Canada
On Wed, Dec 14,
It would be very useful if there were a way (perhaps a custom script
parsing the sacct output) to provide the information in the same
format as "scontrol show job"
Has anybody attempted to do that?
On Wed, Dec 14, 2022 at 1:25 AM Will Furnass wrote:
>
> If you pipe output into 'less -S' then
Ugh. Guess I cannot count. The mapping on that last node DOES work with
the "alternating" scheme where we have
0 0
1 2
2 4
3 6
4 8
5 10
6 12
7 14
8 16
9 18
10 20
11 22
12 1
13 3
14 5
15 7
16 9
17 11
18 13
19 15
20 17
21 19
22 21
23 23
so CPU_IDs=8-11,20-23 does correspond
Hello,
We've been working on upgrading from slurm 20 to the latest slurm 22
and ran into the issue of extremely slow database schema migration. One
workaround I found a reference to suggested just starting slurm 22 with
a fresh database and converting the old database offline and importing
later.
Yes, I see that on some of my other machines too. So apicid is definitely
not what SLURM is using but somehow just lines up that way on this one
machine I have.
I think the issue is cgroups counts starting at 0 all the cores on the
first socket, then all the cores on the second socket.
If you pipe output into 'less -S' then you get horizontal scrolling.
Will
On Wed, 14 Dec 2022, 07:03 Chandler Sobel-Sorenson, <
chand...@genome.arizona.edu> wrote:
> Is there a recommended way to read output from `sacct` involving `-l` or
> `--long` option? I have dual monitors and shrunk the
11 matches
Mail list logo
