Sizing recommendations for KSC for connecting VDI hosts [KSC for Windows]

[Antipova Anna]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials.

Dynamic hosts require more KSC resources than regular hosts.

When a new host is connected to KSC (and the dynamic host is considered new), an icon and a new entry in the database are created, full synchronization with the agent is performed, and the host moved to a group. When the host is deleted, all information about it is deleted as well.
These operations consume a lot of KSC resources, while static hosts require them to be performed only once.
 

Recommended sizing (no more than 20 000 VDI hosts) may not be fully and correctly loaded.

In industrial use, for each icon the following network lists are created: 
- hardware
- installed software
- detected vulnerabilities
- events and lists of executable files of the Application control component.

Size of these lists directly affects KSC performance as well as SQL server performance when performing internal procedures, and the load may grow in the non-linear way. If the use of the solution with your policy settings, environment and virtual desktop properties shows moderate consumption of resources during standard operations, then the number of managed VDI hosts can be increased up to the limit of resources available in the current configuration. Consumption of 80% of memory and 75-80% of available cores is considered moderate.