Check the number of resources allocated to your application by looking at the "Current allocation" value on the page for the consumer associated with your application. If your current allocation is not what you expect, continue reading to find out why you may be experiencing this problem.
Navigate to the tab in the Platform Management Console and check the number of resources your application deserves by looking at the "Guaranteed" value for the consumer associated with your application. If the Guaranteed value does not match your expectation, you are having a related problem. Refer to Why is the number of guaranteed resources for my application lower than what I expect? for more information.
Navigate to in the Platform Management Console and check the demand for the consumer associated with your application (green bar). If the demand is not what you expect, verify that your application is configured to request the number of resources you expect by examining the taskHighWaterMark in your application profile. TaskHighWaterMark is a ratio that is used to determine whether more CPU slots need to be requested to meet the service level agreement of the application. It is a ratio of unprocessed tasks to CPU slots. If the ratio of unprocessed tasks to CPU slots exceeds the taskHighWaterMark, more resources will be requested for the application. Ensure that your rate of request is configured as expected. If your application's resource demand does not match your expectation, modify the taskHighWaterMark for your application. By default, taskHighWaterMark is 1.0 which means that for every 1 unprocessed task, 1 CPU slot is requested.
If your application is pre-started (preStartApplication=true in your application profile), your application’s SSM immediately requests numOfPreloadedServices slots, as defined in your application profile. Any slots required beyond numOfPreloadedServices are requested as needed according to taskHighWaterMark.
Check that there are no blocked hosts for your application. If a host is blocked for your application, EGO cannot allocate that host back to your application until it is explicitly unblocked. If a host is blocked, you have no resources or fewer resources than expected serving your application, more tasks in the PENDING state, and workload completes at a slower rate. Refer to Why are there blocked hosts for my application? for more information.
The remaining section only applies to Symphony grid-mode, and only if you have explicitly configured resource groups, explicitly modified your resource plan, or modified the resReq or resourceGroupName string in your application profile. If you have not done any of those items, you can skip the rest.
If the Resource Selection Method is Dynamic, make sure that the resource requirement string field contains the appropriate selection criteria for this resource group. Modify the resource requirement string, if necessary.
If the Resource Selection Method is Static, make sure that the host list contains all of the hosts that you would like in this resource group. Modify this list, if necessary.