Note: The actual number of slots requested with MaxInstances/MaxInstancesPerSlot may be adjusted depending on the values of MaxInstancesPerSlot and MaxInstancesPerHost. For EGO service instances, the number of slots provided on each host is a fixed amount determined by MaxInstancesPerHost/MaxInstancesPerSlot. If the number of slots requested is not a multiple of the fixed amount, extra slots will be needed to fill the gap and thus be wasted. Take the following configuration as an example:
<sc:MaxInstances>10</sc:MaxInstances>
<sc:MaxInstancesPerSlot>1</sc:MaxInstancesPerSlot>
<sc:MaxInstancesPerHost>6</sc:MaxInstancesPerHost>
Ideally 10 slots (MaxInstances/MaxInstancesPerSlot) are needed. However, the integer value of MaxInstancesPerHost/MaxInstancesPerSlot (fixed amount) is 6 and thus EGO will allocate 12 slots instead of 10, causing two slots to be wasted. To prevent slot wastage, ensure MaxInstances is a multiple of MaxInstancesPerHost/MaxInstancesPerSlot.