Нестабильная задержка Wi-Fi

Question

У меня странные проблемы с задержкой при подключении к сети.

Вот результаты пинга сервера Google, то же самое касается любого удаленного сервера, который позволяет пинговать.

C:\Users>ping -t -l 1000 8.8.8.8

Pinging 8.8.8.8 with 1000 bytes of data:
Reply from 8.8.8.8: bytes=1000 time=97ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=118ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=137ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=45ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=43ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=35ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=96ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=105ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=117ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=135ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=43ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=64ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=74ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=93ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=102ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=115ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=144ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=47ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=69ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=71ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=74ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=102ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=116ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=40ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=42ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=61ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=71ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=81ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=101ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=111ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=131ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=39ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=50ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=70ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=81ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=202ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=109ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=129ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=139ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=57ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=32ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=93ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=105ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=124ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=134ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=52ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=61ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=81ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=92ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=103ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=125ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=134ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=51ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=60ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=75ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=97ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=109ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=136ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=144ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=47ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=58ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=72ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=70ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=100ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=121ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=128ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=38ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=58ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=69ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=89ms TTL=54
Reply from 8.8.8.8: bytes=1000 time=97ms TTL=54

Ping statistics for 8.8.8.8:
    Packets: Sent = 71, Received = 71, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 202ms, Average = 88ms
Control-C

Я также заметил увеличение частоты, которая внезапно падает до ~ 35 мс и повторяется регулярно.

Мой ноутбук - Acer V 17 с беспроводным адаптером Qualcomm Atheros QCA61x4. Я попытался обновить драйвер до версии 12.0.0.230 без разницы.

Если я использую проводной ПК, средняя задержка до 8.8.8.8 составляет 25 мс с минимальным отклонением. Даже при пинге с моим телефоном Android через ту же беспроводную сеть задержка колеблется от 25 до 35 мс. Я даже попробовал другой ноутбук в другой комнате гораздо дальше от маршрутизатора, и он стабильно работает 25 мс с случайной потерей пакета из-за вероятного расстояния.

Когда я пингую локальный шлюз с ноутбука по беспроводной сети, он выглядит довольно нормально:

C:\Users\David>ping -t -l 1000 10.0.0.138

Pinging 10.0.0.138 with 1000 bytes of data:
Reply from 10.0.0.138: bytes=1000 time=3ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=4ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=3ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=4ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=14ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=11ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=9ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=5ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=8ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=3ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=8ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=8ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=5ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=71ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=11ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=4ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=8ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=5ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=9ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=8ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=7ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=15ms TTL=255
Reply from 10.0.0.138: bytes=1000 time=6ms TTL=255

Ping statistics for 10.0.0.138:
    Packets: Sent = 97, Received = 97, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 71ms, Average = 7ms
Control-C

Мой Wi-Fi роутер Zyxel vmg1312 от интернет-провайдера, но, как я уже сказал, проблема до сих пор касается только моего ноутбука. Я использую Windows 10 build 10586 на ПК и ноутбуке.

Изменить: Попытка подключения с помощью провода - нет проблем. Вскоре после подключения через Wi-Fi через некоторое время он работал нормально, а затем снова начал колебаться.

попробовал это решение, снова работает на несколько пингов, затем возвращается:

C:\Users\David>ping -t 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=24ms TTL=54
Reply from 8.8.8.8: bytes=32 time=22ms TTL=54
Reply from 8.8.8.8: bytes=32 time=22ms TTL=54
Reply from 8.8.8.8: bytes=32 time=22ms TTL=54
Reply from 8.8.8.8: bytes=32 time=21ms TTL=54
Reply from 8.8.8.8: bytes=32 time=95ms TTL=54
Reply from 8.8.8.8: bytes=32 time=49ms TTL=54
Reply from 8.8.8.8: bytes=32 time=62ms TTL=54
Reply from 8.8.8.8: bytes=32 time=66ms TTL=54
Reply from 8.8.8.8: bytes=32 time=81ms TTL=54
Reply from 8.8.8.8: bytes=32 time=37ms TTL=54
Reply from 8.8.8.8: bytes=32 time=105ms TTL=54
Reply from 8.8.8.8: bytes=32 time=114ms TTL=54
Reply from 8.8.8.8: bytes=32 time=123ms TTL=54
Reply from 8.8.8.8: bytes=32 time=51ms TTL=54
Reply from 8.8.8.8: bytes=32 time=37ms TTL=54
Reply from 8.8.8.8: bytes=32 time=46ms TTL=54
Reply from 8.8.8.8: bytes=32 time=54ms TTL=54
Reply from 8.8.8.8: bytes=32 time=51ms TTL=54
Reply from 8.8.8.8: bytes=32 time=71ms TTL=54
Reply from 8.8.8.8: bytes=32 time=90ms TTL=54
Reply from 8.8.8.8: bytes=32 time=102ms TTL=54
Reply from 8.8.8.8: bytes=32 time=108ms TTL=54
Reply from 8.8.8.8: bytes=32 time=117ms TTL=54
Reply from 8.8.8.8: bytes=32 time=128ms TTL=54
Reply from 8.8.8.8: bytes=32 time=34ms TTL=54
Reply from 8.8.8.8: bytes=32 time=43ms TTL=54
Reply from 8.8.8.8: bytes=32 time=53ms TTL=54
Reply from 8.8.8.8: bytes=32 time=63ms TTL=54
Reply from 8.8.8.8: bytes=32 time=81ms TTL=54
Reply from 8.8.8.8: bytes=32 time=44ms TTL=54
Reply from 8.8.8.8: bytes=32 time=41ms TTL=54

Ping statistics for 8.8.8.8:
    Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 128ms, Average = 64ms
Control-C

Точно то же самое происходит, когда я перезагружаю сервис WlanSvc с помощью диспетчера задач. Это работает некоторое время, затем возвращается.

Answer 1

Проблема решена, это были настройки управления питанием. Если у вас возникли те же проблемы, попробуйте зайти в Control Panel -> Power managment -> schema settings (for the one selected) -> Advanced settings -> Wireless adapter и изменить его на максимальную производительность.

Я получил локализованные окна, поэтому путь может не совпадать точно.