Why should disk and network I/O be used to identify bottlenecks?

While logons involve some I/O, a high volume of user logons is more directly associated with CPU and memory utilization on the Delivery Controller as the primary indicators.

High disk I/O on the Delivery Controller often reflects heavy logging, database operations, or configuration changes, while high network I/O indicates significant data transfer related to session brokering or policy application. Both can cause delays for target devices or other VDI components that rely on the controller for information or connectivity.

Processor-intensive tasks primarily consume CPU, not necessarily driving high disk and network I/O to the point of being a primary bottleneck indicator for those specific resources.

While malware can cause high I/O, it is a less common and less specific indicator for general performance bottleneck analysis compared to the primary function of the Delivery Controller in a VDI environment.