Your system license limits grants you a number of service units. These limit how and where you can run services and jobs.
- For services, each service costs a certain number of service units per instance to run. For example, a service with a cost of one service unit that's running on three instances counts for three service units against your licensed limit.
- For jobs, service unit cost is assessed based on where job types are allowed to run, not on the number of individual jobs that you run.
Each job type has its own service unit cost. If an instance is configured to run multiple job types, only the job type with the highest service unit cost counts.
For example, suppose that your system has four instances and supports two job types: X, which costs 50 service units, and Y, which costs 25. Job type X is configured to run on three instances. Job type Y is configured to run on those same three instances, plus an additional instance (for a total of four instances). In this case, your total service unit cost for jobs is equal to:
50 + 50 + 50 + 25 = 175
Best practices for service unit limits
The system makes recommendations on the maximum number of service units that you should run on each instance. An instance that runs more than the recommended number of service units in use is likely to experience decreased performance.
The recommended service unit limits are based on whether an instance meets the recommended hardware requirements:
- If an instance meets the recommended hardware requirements, you can run up to 180 service units on that instance.
- If an instance does not meet the recommended hardware requirements, you can run up to 100 service units on that instance.