[Feature Request] Dynamic bandwidth sharing with priorities in delay pools

--===============7437470600124184142==
Content-Type: multipart/alternative; boundary="0000000000000d0477065838a17f"

--0000000000000d0477065838a17f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

 Hello Squid team,

First of all, thank you for maintaining such a robust and reliable proxy
server. We have been using Squid in production for years in a small network
with limited bandwidth (4 Mbps, about 15 users).

Current situation:
We use delay pools to share bandwidth fairly among users. The "class 1"
pool does a decent job of dynamic sharing, but it lacks true QoS features
like:

1. Traffic prioritization (e.g., web browsing > social media > downloads)
2. Burst support with borrow (when one class is idle, others can use its
bandwidth)
3. Per-user fair queuing (not just per-connection)

What we had to do:
We ended up using multiple delay pools (one for web, one for downloads) as
a workaround. But this is not true prioritization - it's just traffic
separation.

Suggestion:
Would it be possible to add HFSC (Hierarchical Fair Service Curve) or
similar queuing disciplines to delay pools? Even a simplified version with:
- Priority levels (high/medium/low)
- Bandwidth borrowing between classes
- Fair queuing per client IP

This would make Squid's QoS capabilities comparable to what pfSense,
MikroTik, and Linux tc offer at the network level, but at the application
layer where Squid operates.

I understand this is not a trivial request, but even a basic implementation
would be a game-changer for small networks with limited bandwidth.

Thank you for considering this suggestion. Keep up the great work!

Best regards,
Yoan Manuel Garc=C3=ADa Lle=C3=B3
Network Administrator

--0000000000000d0477065838a17f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">
Hello Squid team,<br><br>First of all, thank you for maintaining such a=20
robust and reliable proxy server. We have been using Squid in production
 for years in a small network with limited bandwidth (4 Mbps, about 15=20
users).<br><br>Current situation:<br>We use delay pools to share=20
bandwidth fairly among users. The &quot;class 1&quot; pool does a decent jo=
b of=20
dynamic sharing, but it lacks true QoS features like:<br><br>1. Traffic pri=
oritization (e.g., web browsing &gt; social media &gt; downloads)<br>2. Bur=
st support with borrow (when one class is idle, others can use its bandwidt=
h)<br>3. Per-user fair queuing (not just per-connection)<br><br>What we had=
 to do:<br>We
 ended up using multiple delay pools (one for web, one for downloads) as
 a workaround. But this is not true prioritization - it&#39;s just traffic=
=20
separation.<br><br>Suggestion:<br>Would it be possible to add HFSC=20
(Hierarchical Fair Service Curve) or similar queuing disciplines to=20
delay pools? Even a simplified version with:<br>- Priority levels (high/med=
ium/low)<br>- Bandwidth borrowing between classes<br>- Fair queuing per cli=
ent IP<br><br>This
 would make Squid&#39;s QoS capabilities comparable to what pfSense,=20
MikroTik, and Linux tc offer at the network level, but at the=20
application layer where Squid operates.<br><br>I understand this is not a
 trivial request, but even a basic implementation would be a=20
game-changer for small networks with limited bandwidth.<br><br>Thank you fo=
r considering this suggestion. Keep up the great work!<br><br>Best regards,=
<br>Yoan Manuel Garc=C3=ADa Lle=C3=B3<br>Network Administrator

</div>

--0000000000000d0477065838a17f--

--===============7437470600124184142==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
squid-users mailing list
[email protected]
https://lists.squid-cache.org/listinfo/squid-users

--===============7437470600124184142==--