IaaS users are reporting longer than expected wait times when accessing the virtual file repository. There are more than 2TB of free disk space, and vCPU and vRAM do not reach more than 75%…

Increasing disk space will not resolve a performance bottleneck when over 2TB of free space already exists; storage capacity is not the limiting factor.

Although the VM's vCPU and vRAM are under 75%, the physical host running those VMs may be oversubscribed with many tenant workloads competing for the same hardware resources. Checking the host machine's CPU and RAM through the cloud services portal can reveal hypervisor-level contention - such as CPU ready time or memory ballooning - that degrades I/O throughput for all VMs on that host, causing the longer wait times reported when accessing the virtual file repository.

Reviewing historical performance numbers is a useful investigative step but does not directly identify the root cause; it describes when the problem appeared, not what is causing it.

Checking security logs for access denied requests addresses authorization failures, not performance degradation, and is unrelated to the slow file repository access being reported.