That should rule out any unoptimized TCP settings as the cause. The driver versions for the network card were also identical.īefore measuring the network throughput between the workstations using PsPing64.exe, he reset the TCP stack, ran his TCP optimization script, restarted Windows, and then measured. Both computers were equipped with a 10 Gigabit NIC. Test scenario with 2 workstationsĪs a test scenario, Alexander had two high-performance workstations, one with Windows 11 22H2 Enterprise, and one with Windows 10 Pro 22H2 (both on current patch level) connected directly with a patch cable. He sent me his findings over the weekend (thanks for that) and I'll try to summarize them in two blog posts. During tests he found another big problem in Windows 11 when transferring data over a network. Blog reader Alexander, aka MysticFoxDE, who wrote a script for the optimization, stayed on the topic. This can definitely improve network performance noticeably. Within the article I pointed also out the possibility of optimizing this by adjusting the TCP parameters. I recently reported on the problem of Microsoft's "de-optimization" of the TCP stack in the blog post Microsoft's TCP mess, how to optimize in Windows 10/11. In Part 1, I prepare the topic and outline what came out of the measurements. A blog reader has done various experiments and left the results to me. Or in short, in Windows 11, there is a significant performance problem in network transfer when data is received. In addition, the data transfer performance of a TCP/IP connection depends on the direction of the data transfer. If you copy data between machines with Windows 10 and Windows 11, Windows 11 consumes 2 to 3 times more CPU power than Windows 10. When transferring data over a network, Windows has an amazing but unattractive effect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |