Grid Engine will only schedule such a job to a machine that can host the maximum number. Grid Engine will only schedule such a job to a machine that can host the maximum number of slots. Check out "allocation_rule" in the configuration for the parallel environment; either with that or then by specifying $pe_slots for. Hello all, I am testing for the first time the core binding capabilities of SGE. [HOST] › archive:parallel_environment. $pe_slots - place all the job slots on a single machine. Monitoring/Accounting - ability to monitor all submitted jobs and query which cluster nodes they're running on, whether they're finished, encountered an error. $pe_slots – place all the job slots on a single machine. . A positive integer fixes the number of processes for each suitable host. Urgency Slots. $fill_up: Slots are allocated to fill up the most appropriate node before spilling into. $pe_slots: Number of slots granted for the job. Use the special denominator $pe_slots to cause the full range of processes of a job to. $pe_slots: All slots are allocated to a single node. $fill_up: $round_robin. Use the special denominator $pe_slots to cause all the processes of a job to be allocated on a single host (SMP). I want all my non-parallel environment jobs to have a core. The allocation rule $pe_slots requires you to submit jobs that are of the exact same size as the number of cores on any of your machines. $processors: The processors string as contained in the queue configuration (see queue_conf(5)) of the master.