From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.github.com (out-18.smtp.github.com [192.30.252.201]) by mail.toke.dk (Postfix) with ESMTPS id D580785A0D0 for ; Tue, 22 Jun 2021 15:52:08 +0200 (CEST) Authentication-Results: mail.toke.dk; dkim=pass (1024-bit key) header.d=github.com header.i=@github.com header.b=rIhWETyY Received: from github.com (hubbernetes-node-f90a96e.va3-iad.github.net [10.48.122.40]) by smtp.github.com (Postfix) with ESMTPA id 08CFD340228 for ; Tue, 22 Jun 2021 06:52:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1624369927; bh=lXmhuqYfgZZosSWG5ay3mwUqanTlTpl3VKmdZQCcdO8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rIhWETyYmRfRwz84VS5Jh6LJYbYB4FyCqD4dREFoHX+ZpXsvUTERMZJ64wtfJR2s4 cgE4pZpasTOSjaAyHWvbBSOc1e9Rz7zBH9z7habPy+15P6fqg9kw2KxQ/5E57OKOD3 qcHH8d1qtSrIIU67tP38nNqgLxVQdR9qQFRKQplo= Date: Tue, 22 Jun 2021 06:52:07 -0700 From: "Kirill Lukonin (EvilWirelessMan)" To: tohojo/flent Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_60d1eb0762af_57c6fc21512"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: klukonin X-GitHub-Recipient: flent-users X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: flent-users@flent.org Message-ID-Hash: NTOWMO4ONBFLU5SIO4ECGGKSTI2O5RAP X-Message-ID-Hash: NTOWMO4ONBFLU5SIO4ECGGKSTI2O5RAP X-MailFrom: noreply@github.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Subscribed X-Mailman-Version: 3.3.4 Reply-To: tohojo/flent Subject: [Flent-users] Re: [tohojo/flent] Plots are broken somehow (#227) List-Id: Flent discussion list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: ----==_mimepart_60d1eb0762af_57c6fc21512 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello, Dave. It's not a network issue. Bluetooth/Wi-Fi scanning cause these spikes. But honestly, I did a lot of research about current Android network kitchen. There are a lot of to improve. You see a test results of SberDevices SberBox early release (unpatched firmware). Current release is better a lot, because we did so much work to decrease latency and improve stability of Wi-Fi connection. I can say that scanning and roaming are two main diseases of android TV boxes/sticks. RTT could be up to 2000+ms. We can discuss it in the mailing list, but not here =) Hope to share soon our results and Flent extensions for Android devices. Actually, It's a good chance to say thank you, because some years ago your articles inspired me to learn more about traffic and queues. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/227#issuecomment-866002891 ----==_mimepart_60d1eb0762af_57c6fc21512 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Hello, Dave.

It's not a network issue. Bluetooth/Wi-Fi scanning cause these spikes. But honestly, I did a lot of research about current Android network kitchen. There are a lot of to improve. You see a test results of SberDevices SberBox early release (unpatched firmware).
Current release is better a lot, because we did so much work to decrease latency and improve stability of Wi-Fi connection. I can say that scanning and roaming are two main diseases of android TV boxes/sticks. RTT could be up to 2000+ms. We can discuss it in the mailing list, but not here =)

Hope to share soon our results and Flent extensions for Android devices.

Actually, It's a good chance to say thank you, because some years ago your articles inspired me to learn more about traffic and queues.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

----==_mimepart_60d1eb0762af_57c6fc21512--