Adaptive Load Balancing, Windows 7/x64
2 NICs/team (X520-T2 and X540-T2), 4 nodes with one team each.
2 xs708ev2 switches, one connection per team per switch.
One NIC is always inactive.
Running current releases of Intel's Fortran and MPI on both CentOS7 and Windows 7 on the same nodes. Using one or the other system, not intermixing.
On same gear, CentOS 7 makes use of both NICs.
Same benchmark on Windows 7 (Class D FT, NPB) walltime=400s. On CentOS 7, walltime = 308s.
Running the same code on a single node using 16 cores to avoid network traffic (all messaging uses SHM):
Windows 7 walltime = 370s.
CentOS 7 walltime = 370s.
Casual observation of the switches: Windows 7 doesn't make use of the second switch but CentOS 7 does.
Here's my team_config entry for CentOS 7:
TEAM_CONFIG='{"runner": {"fast_rate": true, "name": "loadbalance","tx_hash": ["ipv4"],"tx-balancer": {"name": "basic"}}, "ports": {"enp2s0f0": {}, "enp2s0f1": {}}}'
Would like to make use of both NICs in each team under Windows. Oh, if both of the team's NICs are connected to the same switch, then both NICs will be actively used.
Message was edited by: Art Lazanoff each switch is configured with VLAN and LAG disabled. When both connections in a ALB are connected the same switch, both NICs are active, Windows task manager shows a 20gbps data rate, and clock time for the test program improves by about 40s. The ALB's "test switch" diagnostic reports no errors. Individually both switches perform the same way. When a team is connected using NIC-1 to switch 1 and NIC-2 to switch 2, The ALB "test switch" diagnostic reports "The switch is configured with aggregated ports, but the team type does not support port aggregation. The switch is configured with VLAN tagging, but the team has no VLANs. Reconfigure the switch for link aggregation, or disable VLAN tagging on the switch. "