FAQs for host scavenging

In Windows, what actions trigger the closing of desktop hosts and reclaiming of work during host scavenging?

The user idle time is only affected by local physical mouse or keyboard movements/actions. The movement of a remote client’s or terminal server client's mouse/keyboard does NOT affect the user idle time.

Does EGO allocate slots to a consumer from a scavenge resource group first or last?

During processing, EGO considers the order in which resource groups are stored in ResourceGroups.xml. The order is based on when the resource group was created (that is, the first resource group created gets processed first). If you want to ensure that scavenge-ready hosts are processed last (for example, slots are not allocated from scavenge-ready hosts in a scavenge resource group until hosts from all other resource groups are first considered by EGO), do not create a scavenge resource group until you have created all other resource groups.

Assuming that when you create your resource groups that you create a scavenge group last, the processing order is as follows:

Resource Group A (created first)

Resource Group B (created second)

Resource Group C, made up of scavenge-ready hosts (created last)

All guaranteed allocations processed first

1st --->

2nd --->

3rd --->

All reclaim requests processed second

4th --->

5th --->

6th --->

All borrowing requests processed last

7th --->

8th --->

9th (last)

Following this recommended processing order, EGO allocates slots to a consumer from a scavenge resource group after processing other resource groups first. Likewise, EGO processes reclaim requests and borrows hosts from a scavenge resource group last.

If you created a scavenge resource group during installation without considering the creation order, you can manually edit ResourceGroups.xml and re-order the groups. There is some risk involved in editing this file, so it is best to contact Platform Technical Support for assistance.