{"action":"created","issue":{"url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/4209","labels_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/4209/labels{/name}","comments_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/4209/comments","events_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/4209/events","html_url":"https://github.com/qbittorrent/qBittorrent/issues/4209","id":119558663,"number":4209,"title":"Periodic latency spikes since version 3.3.0","user":{"login":"Gargauth","id":4639696,"avatar_url":"https://avatars.githubusercontent.com/u/4639696?v=3","gravatar_id":"","url":"https://api.github.com/users/Gargauth","html_url":"https://github.com/Gargauth","followers_url":"https://api.github.com/users/Gargauth/followers","following_url":"https://api.github.com/users/Gargauth/following{/other_user}","gists_url":"https://api.github.com/users/Gargauth/gists{/gist_id}","starred_url":"https://api.github.com/users/Gargauth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Gargauth/subscriptions","organizations_url":"https://api.github.com/users/Gargauth/orgs","repos_url":"https://api.github.com/users/Gargauth/repos","events_url":"https://api.github.com/users/Gargauth/events{/privacy}","received_events_url":"https://api.github.com/users/Gargauth/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/qbittorrent/qBittorrent/labels/Performance","name":"Performance","color":"444444"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2015-11-30T19:07:44Z","updated_at":"2015-12-14T01:47:23Z","closed_at":null,"body":"After upgrading to latest version (3.3.0) I noticed periodic and very frequent latency spikes (jitter) when QBittorent is running.\r\n\r\nWhat I found so far:\r\n- Every ~10 seconds ping increases to around 200-1000 ms for one and occasionally two consecutive packets\r\n- Occurs in both WAN and LAN (ping router, ap, ...)\r\n- Occurs even if QBittorent is blocked in Windows Firewall (both directions)\r\n- Occurs after fresh QBittorent installation with everything set to default and no torrents active\r\n- Occurs regardless of network interface (tried two different wireless usb dongles)\r\n- Occurs even if all other networking adapters are disabled (VMware adapters, ethernet adapters)\r\n\r\n\r\nI run Windows 10 x64, using Wifi USB adapters (can't connect by ethernet cable to test, unfortunately).\r\n\r\nI realize that Wireless performance can be volatile by its nature, but this is happening very reliably very shortly after launching Qbittorent until it's terminated. My ping is otherwise very stable, 1-2 ms in LAN. I tried older versions (3.2.0 and 3.2.5) with no jitter problems. \r\n\r\nPing output looks like this when Qbittorent is running (notice how it happens every 10th packet):\r\n```\r\n> ping 192.168.1.1 -t\r\n\r\nPinging 192.168.1.1 with 32 bytes of data:\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=4ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=2ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=736ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=2ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=3ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time<1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=688ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time<1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=2ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=2ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=679ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=2ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=631ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\nReply from 192.168.1.1: bytes=32 time=1ms TTL=64\r\n\r\nPing statistics for 192.168.1.1:\r\n    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),\r\nApproximate round trip times in milli-seconds:\r\n    Minimum = 0ms, Maximum = 736ms, Average = 69ms\r\n```"},"comment":{"url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/comments/164320919","html_url":"https://github.com/qbittorrent/qBittorrent/issues/4209#issuecomment-164320919","issue_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/4209","id":164320919,"user":{"login":"arvidn","id":661450,"avatar_url":"https://avatars.githubusercontent.com/u/661450?v=3","gravatar_id":"","url":"https://api.github.com/users/arvidn","html_url":"https://github.com/arvidn","followers_url":"https://api.github.com/users/arvidn/followers","following_url":"https://api.github.com/users/arvidn/following{/other_user}","gists_url":"https://api.github.com/users/arvidn/gists{/gist_id}","starred_url":"https://api.github.com/users/arvidn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arvidn/subscriptions","organizations_url":"https://api.github.com/users/arvidn/orgs","repos_url":"https://api.github.com/users/arvidn/repos","events_url":"https://api.github.com/users/arvidn/events{/privacy}","received_events_url":"https://api.github.com/users/arvidn/received_events","type":"User","site_admin":false},"created_at":"2015-12-14T01:47:23Z","updated_at":"2015-12-14T01:47:23Z","body":"does this happen if you disable the DHT too? the first thought that comes to mind is DHT bootstrapping or maintenance traffic.\r\n\r\nWireshark would probably shed some light on what kind of traffic is being send to cause this. (I'm guessing it's some traffic spend spike).\r\n\r\ndid 3.3.0 update libtorrent version?"}}