ISchedulerJob::MaximumNumberOfCores property
Retrieves or sets the maximum number of cores that the scheduler may allocate for the job.
This property is read/write.
Syntax
HRESULT put_MaximumNumberOfCores(
[in] long maxCores
);
HRESULT get_MaximumNumberOfCores(
[out] long *pMaxCores
);
Property value
The maximum number of cores.
Error codes
If the method succeeds, the return value is S_OK. Otherwise, the return value is an error code. To get a description of the error, access the ISchedulerJob::ErrorMessage property.
Remarks
Set this property if the ISchedulerJob::UnitType property is JobUnitType_Core.
If you set this property, you must set the ISchedulerJob::AutoCalculateMax property to VARIANT_FALSE; otherwise, the maximum number of cores that you specified will be ignored.
The Default job template sets the default value to 1.
This property tells the scheduler that the job requires at most n cores to run (the scheduler will not allocate more than this number of cores for the job).
The job can run when its minimum resource requirements are met. The scheduler may allocate up to the maximum specified resource limit for the job. The scheduler will allocate more resources to the job or release resources if the ISchedulerJob::CanGrow or ISchedulerJob::CanShrink properties are set to VARIANT_TRUE; otherwise, the job uses the initial allocation for its lifetime.
The property value cannot:
- Exceed the number of cores in the cluster or the number of cores on the nodes that you requested (with the ISchedulerJob::RequestedNodes property).
- Be less than the value of the ISchedulerJob::MinimumNumberOfCores property.
Requirements
Product |
HPC Pack 2008 R2 Client Utilities, HPC Pack 2008 Client Utilities |
Type library |
Microsoft.Hpc.Scheduler.tlb |
See also
ISchedulerJob.MaximumNumberOfNodes