Reuti <[email protected]> writes:
>> That isn't getting to my question though. The man page says "the number of
>> slots reserved for the job is the number of slots requested with the -pe
>> switch + 1". But I don't see any evidence of that, unless I don't
>> understand what "slots reserved" means. If I submit a -pe 8 job, it will
>> run on a host with 8 slots. As near as I can tell, the parenthetical
>> remarks should just be removed.
>
> Aha, I see. Yes indeed, the wording is confusing.
I modified it, but it's not yet pushed to the web site.
Job_is_first_task
The job_is_first_task parameter can be set to TRUE or FALSE. A value
of TRUE indicates that the xxQS_NAMExx job script already contains
one of the tasks of the parallel application (and the number of
slots reserved for the job is the number of slots requested with the
-pe switch). FALSE indicates that the job script (and its child
processes) is not part of the parallel program (e.g. the job is
using mpirun(1)) and the number of slots reserved for the job in the
master queue is increased by 1, as indicated by qstat/qhost.
If wallclock accounting is used (execd_params ACCT_RESERVED_USAGE
and/or SHARETREE_RESERVED_USAGE set to TRUE) and control_slaves is
set to FALSE, the job_is_first_task parameter influences the
accounting for the job: A value of TRUE means that accounting for
CPU and requested memory gets multiplied by the number of slots
requested with the -pe switch. FALSE means the accounting informa‐
tion gets multiplied by number of slots + 1. Otherwise, the only
significant effect of the parameter is on the display of the job,
but it can be used to indicate, say, mpirun-type job startup.
> Maybe it would be better to say:
>
> job_is_first_task The job_is_first_task... ... The output of `qstat
> -g t`resp. `qhost -q` will describe the allocation for a job running
> in this particular PE according to this setting. I.e. for
> job_is_first_task set to FALSE it will list one slot more to reflect
> the idling main job script for this job. It will also allow one
> additional `qrsh -inerherit ...` to be made in this case to spawn the
> necessary number of slave tasks.
How can you run an additional qrsh as the extra slot is on the master?
> Nevertheless the overall consumed
> slot count is still the same independent of this setting.
--
Community Grid Engine: http://arc.liv.ac.uk/SGE/
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
