Our Windows machines have historically been slower when running LDAP tests. Some of our LDAP tests rely on injecting timeouts and network faults to test the server's resilience in these situations. Since Windows is slower, timeouts tend to occur more frequently.

ldap_failover_degraded_performance.js moves a fleet of LDAP servers into various states - slow, timeout, or normal - and asserts that LDAP authentication on MongoDB behaves as expected. It allows for a certain error margin of unexpected authentication results to account for the risk of clients connecting to a slow or downed LDAP server, which can skew the number of auth failures.

Since Windows adds a certain level of intrinsic slowness to the LDAP servers, we should increase the error margin and also possibly reduce the overall number of FSM states that this test goes through on Windows to reduce flaky BFs.