From: David Collier-Brown <davec-b@rogers.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Detecting "fake" bandwidth from ISPs
Date: Sun, 8 Jun 2025 07:25:52 -0400 [thread overview]
Message-ID: <305b763e-3dd8-4f39-8c9c-4066ea13d27b@rogers.com> (raw)
In-Reply-To: <305b763e-3dd8-4f39-8c9c-4066ea13d27b.ref@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
ISPs sometimes offer more performance when a customer is doing a load
test than any other time. The authors of this paper use a
machine-learning model to detect "fake" bandwidth using 20 days of logs.
www.researchgate.net
(PDF) Optimisation of Network Logs for Fake Bandwidth Classification
using CNN <#>
PDF | The goal of this study is to enhance the classification accuracy
of fake bandwidth using a CNN model, leveraging network logs collected
in... | Find, read and cite all the research you need on ResearchGate
🔗
https://www.researchgate.net/publication/392480826_Optimisation_of_Network_Logs_for_Fake_Bandwidth_Classification_using_CNN
<https://www.researchgate.net/publication/392480826_Optimisation_of_Network_Logs_for_Fake_Bandwidth_Classification_using_CNN>
The work also looks at the possibility of using the "real" bandwidth
to guide allocation and keep the QoS high
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 2823 bytes --]
parent reply other threads:[~2025-06-08 11:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <305b763e-3dd8-4f39-8c9c-4066ea13d27b.ref@rogers.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=305b763e-3dd8-4f39-8c9c-4066ea13d27b@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox