Hi Ole,
Ole Holm Nielsen writes:
> Hi Loris,
>
> On 9/26/22 12:51, Loris Bennett wrote:
>>> When designing restriction in job_submit.lua, I found there is no member in
>>> job_desc struct can directly be used to determine the node number finally
>>> allocated to a job. The job_desc.min_nodes s
Am 9/26/22 um 13:04 schrieb Josef Dvoracek:
hello @list!
anyone who was dealing with following scenario?
* we have limited amount of Matlab network licenses ( and various
features have various amount of available seats, eg. machine learning:
N licenses, Image_Toolbox: M licenses)
* license
It should generally be as much as you need to hold the full database in
memory. That said if you are storing Job Envs and Scripts that will be
a lot of data, even with the deduping they are doing. We've generally
done about 90 GB buffer size here with out much of any issue even though
our dat
Hi Loris,
On 9/26/22 12:51, Loris Bennett wrote:
When designing restriction in job_submit.lua, I found there is no member in
job_desc struct can directly be used to determine the node number finally
allocated to a job. The job_desc.min_nodes seem to
be a close answer, but it will be 0xFFFE
Are your licenses used only for the slurm cluster(s) or are they
shared with laptops, workstations and/or other computing equipment not
managed by slurm?
In the former case, the "local" licenses described in the
documentation will do the trick (but slurm does not automatically
enforce their use, so
hello @list!
anyone who was dealing with following scenario?
* we have limited amount of Matlab network licenses ( and various
features have various amount of available seats, eg. machine learning: N
licenses, Image_Toolbox: M licenses)
* licenses are being used by slurm jobs and by individual
writes:
> Hi all:
>
>
>
> When designing restriction in job_submit.lua, I found there is no member in
> job_desc struct can directly be used to determine the node number finally
> allocated to a job. The job_desc.min_nodes seem to
> be a close answer, but it will be 0xFFFE when user not s
On 9/26/22 08:48, taleinterve...@sjtu.edu.cn wrote:
When designing restriction in job_submit.lua, I found there is no member
in job_desc struct can directly be used to determine the node number
finally allocated to a job. The *job_desc.min_nodes *seem to be a close
answer, but it will be 0x