By using CLI commands, you can check the shadow memory of a vSphere Bitfusion client, the MTU size of your network, and the network interfaces for error statistics and dropped packet counts.
Shadow Memory Check
The vSphere Bitfusion client uses a part of its memory space as a shadow memory of the allocated remote GPU memory. The precise amount of memory required on the client host varies between applications. The shadow memory check determines if the host's memory is as large as the GPU memory. For more information about memory requirements, see the System Requirements for vSphere Bitfusion topic in the VMware vSphere Bitfusion Installation Guide.
You can see the amount of memory on your client from the MemTotal line of the pseudo file /proc/meminfo. To calculate the GPU memory, from a GPU server, you can run the bitfusion smi or nvidia-smi command, and add up the memory sizes of all GPUs.
You can add more memory to the vSphere Bitfusion client to meet the requirement. Alternatively, when you run applications, do not allocate more GPUs than you can shadow in the memory of the vSphere Bitfusion client.
MTU Size Check
The vSphere Bitfusion performance relies on a healthy, low-latency, and high-speed network. Applications perform better when they send a few large packets instead of many small packets. The maximum transfer unit (MTU) check determines whether you have a large (³4K) MTU setting for all high-speed (³10 Gbps) interfaces. Ignore this check for interfaces you do not use with vSphere Bitfusion.
- To check the MTU size, you can run the ifconfig command.
- To change the MTU size on network interface enp175s to 4096 bytes, you can run ifconfig enp175s mtu 4096.
Network Errors Check
You can check the network interfaces for error statistics and dropped packet counts. The files are in the following locations.
If your network is healthy, the error count between the checks does not increase, new error messages do not occur, and no packets are dropped. The files are zeroed out only after a reboot.