Hi, Hahn
I mean the elapsed time.
In the example I mentioned earlier，a job run 10s ，the elapsed time from
sacct is 640s(10s*64), so how do i get the real elapsed time from sacct or
other command line tools?
As you mentioned, i checked usercpu/systemcpu/totalcpu, but they all zero
Query command:
I agree that resetting to a non-zero value would be helpful (vote_count++).
That's how I originally stumbled upon this feature. We bill for system time
based on usage per month, and there are cases where "refunds" need to be
issued. (Usually high-tech issues, like, rebooting the wrong node
Wow, nice find. I wasn't even aware of that one. Hopefully they will
support the ability to reset to other values in the future as that would
be a handy ability.
-Paul Edmon-
On 7/16/2020 12:56 PM, Sebastian T Smith wrote:
`sacctmgr` can be used to reset the accrued RawUsage value.
`sacctmgr` can be used to reset the accrued RawUsage value. Example usage:
# sacctmgr modify user where Account= set RawUsage=0
Review the `sacctmgr` documentation for more details:
https://slurm.schedmd.com/sacctmgr.html
Best,
Sebastian
--
[University of Nevada,
srun -N 1 -n 1 -p testA sleep 10
then the cpurawtime of this job recorded by slurm is 640s, but actually
this job only used 10s;
so, I want to know are there any way to get the real cputime used by this
job in slurm.
if you really mean cpu time (compute-bound, not elapsed),
then don't you just
Also as a side, is there an official name for the other fairshare
system? I guess the official documentation calls it Classic Fairshare,
like Classic Coke :). I hate to call it old as we use it here and will
continue to use it. We have no intention to moving to FairTree because
we've only
A trick you can use to reset certain users (which I have used before) is
to simply delete them from the slurmdb and then readd them. At least
under the other fairshare system, which is what our site uses, that
would remove their usage and they would have 0 usage when they
returned. I'm
Hello,
I will try to explain an scenario that occurs in my SLURM cluster. An important
number of users (accounts) belongs to students of a certain subject. That
subject is 6 month duration. When subject end, I "reset" user folders, clean
all data, reset passwords and, in next academic year, I
Hi, all
In my slurm.conf node selecttype configured as
SelectType=select/linear
Some partitions enabled OverSubscribe as
OverSubscribe=FORCE:64 or OverSubscribe=FORCE:4
Assume a partition named testA with a node has 64 cpu cores,
enabled OverSubscribe with OverSubscribe=FORCE:64.
if I submit a
