While the test itself isn't heavyweight, the fact that it's intentionally timing-sensitive means it can be affected by interference caused by load from other tests. The margins in the test are already very generous, that's not really the problem. The problem is that in evergreen on windows-debug-suggested, the level of load is high enough to make even generous margins fail. Per advice from devprod, tagging it resource_intensive will let it run separately before the other stuff causing heavy load and resolve the issue.