benchmark: readStart only after completion
fix #11972 (closed)
On windows apparently it's meaningful to call readStart
only after connection completion.
(makes sense on POSIX as well, and causes no regressions)
Checklist
-
tests and/or benchmarks are included -
commit message follows [commit guidelines]
Affected core subsystem(s)
benchmarks