○Socket Communicationsについて
Socket Communications — ネットワーク通信のnon-blocking I/Oを有効・無効し
つまり、Provisioning ServerのOS、バージョン、およびサーバーのNICドライバー

PVS 4.5.1 では、non-blocking I/Oを設定する場合、多くのリトライを発生します。
PVS 4.5.2 では、クライアント側でいくつかの重要なアーキテクチャの改善がされ、

Socket Communications — Enable/disable non-blocking I/O for network
communications. Non-blocking sockets generally work more efficiently
(consume fewer CPU cycles) than blocking sockets. Non-blocking sockets
therefore usually increase network throughput. However, non-blocking
sockets also increase the likelihood of dropped packets and therefore tend
to increase device retries. Set to whichever setting works best with your
version of the Provisioning Server OS and server NIC drivers/hardware

PVS 4.5.1 may be causing a lot of retries when using non-blocking I/O. Some major architecture changes on the client in the 4.5.2 release may have made some of these retries go away.

So to clarify:

PVS 4.5.1
Non-Blocking I/O set is causing network utilization to go to 30% (during boot?)
Blocking I/O uses 10% ?

Is this what the ticket is saying, Non-Blocking I/O is meant to decrease the CPU utilization of the PVS server and increase the Network utilization. What are their boot times and retry counts in both scenarios and they precisely explain the testing results and methods of testing?

suggesion at this time is to upgrade 4.5.2