# Successrate vs SQM

**URL:** <https://forum.storj.io/t/successrate-vs-sqm/30885>\
**Category:** Node Operators\
**Tags:** sqm\
**Created:** [September 30, 2025, 11:23pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885 "2025-09-30T23:23:34Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 30, 2025, 11:23pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/1 "2025-09-30T23:23:34Z")

</div>

To SQM or not to SQM?

I have cable internet with 35Mbps upstream bandwidth, which with the recent spike in egress is being saturated at 50Mbps, ramping up latency to 60ms.

Success rates looks quite sad:

 ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/6/3/63aa7d2562daf292fb77868efd4a11bc3851167e.png)

> **Just look at the large files success rate -- under 25%!**
>
> ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/2/4/24e3b3b74ae44758c3d47f618724e63d66e8f995.png)

Enabling SQM with 40Mbps limiter drops latency to 15ms while still saturated, albeit at lower throughput:

 ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/2/8/283eab1d67cb6e09776f6db0a9a93a50006f67fb.png)

> **And the success rate on large files is magnificent now as well! (note scale is now different**
>
> ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/5/0/50f8b295e47b14d1ca6861cd8b9486834b068ac5.png)

Not only success rate is higher, but effective throughput also increased, overall internet browsing speed increased, and everything feels more responsive, while consuming _less_ bandwidth. Because the pipe isn’t bogged down by nonsense.

so, if you don’t SQM – you are missing out. There are no downsides. Turn on SQM now. And if your gateway does not support SQM – perform emergency defenestration and get the one that does.

---

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [October 1, 2025, 3:01am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/2 "2025-10-01T03:01:12Z")

</div>

If I were bandwidth-constrained, I’d probably implement some solution inside storagenode. Like, literally, even something as simple as “don’t continue with a new download (like, reading data from disk) if existing downloads already total up to some threshold uplink bandwidth value”. IIRC per Storj Inc. statements so far that would be acceptable behavior, and would make healthier I/O patterns too (-:

> [@Cancelled audits](https://forum.storj.io/t/cancelled-audits/27351/40):
>
> basically - yes. We would be happy if you can keep it online. But if you couldn’t it’s better to be offline than slow. We want to have a great customers experience: the offline node will be excluded from any node selection.

It does talk about being totally offline though…

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 1, 2025, 4:26am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/3 "2025-10-01T04:26:43Z")

</div>

This will inevitably leave some bandwith unused. aka wasted. That’s why conventional QoS is bad. I want to use 100% of bandwidth. But fairly, and without increasing latency.

---

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [October 1, 2025, 4:47am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/4 "2025-10-01T04:47:23Z")

</div>

Probably depends on whether the “wasted” bandwidth contributes to races won, or lost. If the latter, reducing the threshold would let you win more races.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 1, 2025, 4:58am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/5 "2025-10-01T04:58:26Z")

</div>

Right. Conventional QoS or bandwidth limiting is static, it is designed to partition availale resource and prevent the specific consumer from hogging the whole pipe. But this means that even when there is nobody else wanting to use the resource, the consumer is still prevented from hogging the whole pipe – even though it totally could with no ill effects.

SQM is designed to solve this – give everyone access to full pipe, allow to use evely last bit of bandwith, but prevent overuse and latency spikes.

So both things are true - you want low latency, and you want all available bandwith. SQM give you that. Classis QoS does not.

---

<div class="post-metadata">

**Author:** ![Pentium100](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pentium100/32/6082_2.png) [@Pentium100](https://forum.storj.io/u/Pentium100)\
**Post date:** [October 1, 2025, 7:14am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/6 "2025-10-01T07:14:43Z")

</div>

I’ll just add that this is useful only if your connection is near saturation or saturated. If you have, say, 500mbps connection and the traffic is 30mbps, SQM won’t do anything. It likely won’t hurt, but don’t expect any appreciable success rate increases.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 1, 2025, 9:05am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/7 "2025-10-01T09:05:23Z")

</div>

Absolutely. In fact, it totally _can_ hurt: most providers allow for much higher peak speeds (speed bursting) in the begining of the transfers.

For example, if you have 50Mbps channel, you can see 200Mbps bursts – this improves experience a lot on slow connections. But once you enable SQM – ypu will never see more than 48-49.

You are trading predictability and low latency for bursty peak performance.

So depending on what you do – you can turn it on or off.

My downstream is 1500Mbps. BUt if I enabel SQM – I barely get 800Mbps. My UDMP does not even allow to put anythign above 1000 into the configuration box. But the upstream is just 35Mbps. I do get 50Mbps, with horrible latency. So, for the most part I have SQM On – but if I really need to download something as fast as humanly possible – I temporarily disable it.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 1, 2025, 9:07am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/8 "2025-10-01T09:07:43Z")

</div>

Whoohoo – my refusal to shut up about SQM caused a new tag to be created 😃  
 ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/e/b/eba3c14307f5a730d6fc153debef68a1de97a44e.png)

---

<div class="post-metadata">

**Author:** ![Pentium100](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pentium100/32/6082_2.png) [@Pentium100](https://forum.storj.io/u/Pentium100)\
**Post date:** [October 1, 2025, 10:45am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/9 "2025-10-01T10:45:04Z")

</div>

If your connection is so asymmetric, you can enable SQM just for the outgoing packets. No need to limit the incoming ones (trafic shaping does not work that well on receiving end anyway).

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 1, 2025, 3:11pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/10 "2025-10-01T15:11:18Z")

</div>

You are a genius. There is no way to only enable upstream sqm in UniFi UI, you have to specify both, but I could cheat and delete download queue manually. Will try this today.

Edit. Evidently, I could put 0 as download speed, and it accomplishes the same 🤦. It’s probably a new feature, because it tried it before, and UI would reject it.

> **crazy**
>
> ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/9/5/957685c1b99fc3c636530f34a9e9933985308a21.jpeg)

---

<div class="post-metadata">

**Author:** ![Pentium100](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pentium100/32/6082_2.png) [@Pentium100](https://forum.storj.io/u/Pentium100)\
**Post date:** [October 1, 2025, 6:10pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/11 "2025-10-01T18:10:32Z")

</div>

My router is Linux, I can set queues for each card separately. I have set some priorities on my backup connection, since it is only 10mbps upload, not sqm though.

---

<div class="post-metadata">

**Author:** ![RecklessD](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/recklessd/32/1130_2.png) [@RecklessD](https://forum.storj.io/u/RecklessD)\
**Post date:** [October 1, 2025, 8:33pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/12 "2025-10-01T20:33:39Z")

</div>

SQM or AQM is only effective for buufer bloat when the link on the other side is slower. So, on your downlink, it’s just a waste of CPU cycles (unless your LAN is slower than your Internet downlink).

I see reports that many Ubiqiti devices struggle at speeds over 300M and SQM.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [October 1, 2025, 9:30pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/13 "2025-10-01T21:30:25Z")

</div>

> [@RecklessD](#):
>
> other side is slower

Funny enough, most of my home network is 1 gigabit. And internet is 1.2-1.5Gbps. So yeah 🙂

On the other hand – bufferbloat is not an issue at such speeds because it’s close to design capacity of the equipment.

> [@RecklessD](#):
>
> I see reports that many Ubiqiti devices struggle at speeds over 300M and SQM.

It depends on the device. The original USG-3 woudl max out at 30Mbps. When I had 12 Mbps upstream (lol) that was a lifesaver. USG-4-Pro I think could support up to 250Mbps. My (original) UDMP manages up to 750Mbps at least. But you can’t specify the limit higher than 1000 in the UI, and they don’t recommend using SQM at speeds above 300, so it’s sort of moot. Now that I can put 0 in there – it solved all the problems.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [October 1, 2025, 9:57pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/14 "2025-10-01T21:57:29Z")

</div>

> [@arrogantrabbit](#):
>
> It depends on the device

So true.. I switched from UBNT unifi gateways to [Opnsense](https://opnsense.org/) on a [Protectli V1610](https://eu.protectli.com/product/v1610/) when I was able to get 2.5G internet at home.  
If anyone considers one of these, it’s great but runs a little hot - so I’ve added a [Noctua NV-FS2](https://noctua.at/en/nv-fs2) on top.  
I know.. they’re a marketing company, but this one actually runs dead silent and does the job well - though it’s overpriced.

Even at these speeds, I experienced gains in traffic flow using their much similar FQ-CoDel / FQ-PIE.

It’s causing a small loss in top-speed (100-150mbit) but the gains in responsiveness well outweighs that.

(PS. @arrogantrabbit this is FreeBSD.. 🥳)

---

<div class="post-metadata">

**Author:** ![Pentium100](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pentium100/32/6082_2.png) [@Pentium100](https://forum.storj.io/u/Pentium100)\
**Post date:** [October 2, 2025, 4:13am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/15 "2025-10-02T04:13:15Z")

</div>

It is possible to use somethig like this in the opposite direction, but it’s less than ideal.  
Basically, if I know that my connection is, say, 50mbps, I can use htb or something similar to limit the speed to 49mbps and then use SQM, priorities or whatever. This usually has to be done for upload as well, since the connection speed is slower than the interface speed (10M upload, but 100M interface). Basically, limit the speed so the queues start forming on my router (and not the ISPs equipment or the cable modem) and then manage the queues as I see fit.

---

<div class="post-metadata">

**Author:** ![RecklessD](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/recklessd/32/1130_2.png) [@RecklessD](https://forum.storj.io/u/RecklessD)\
**Post date:** [October 2, 2025, 5:37am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/16 "2025-10-02T05:37:06Z")

</div>

Buffer bloat is usually only going to be a problem where network transitions to a slower speed.

So, if you have a 1G/100M internet connection, and your internal LAN is 100M, desirable on inbound, but will be of little use outbound.

But if your internal LAN is 1G (or higher), you will get much benefit on inbound, but desirable on outbound.

Note: This is only in the context of buffer bloat, there are many other reasons for using Traffic Shaping/QOS/Queue management.

> [@arrogantrabbit](#):
>
> When I had 12 Mbps upstream (lol) that was a lifesaver.

😀. We use to build routers for dial up connections. 14.4k…. Traffic shaping with traffic control, SFQ, Iptables.

---

<div class="post-metadata">

**Author:** ![Pentium100](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pentium100/32/6082_2.png) [@Pentium100](https://forum.storj.io/u/Pentium100)\
**Post date:** [October 2, 2025, 6:16am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/17 "2025-10-02T06:16:56Z")

</div>

> [@RecklessD](#):
>
> Buffer bloat is usually only going to be a problem where network transitions to a slower speed.

Yes, but you can artificially move that spot to have better queue management. For example, let’s say the LAN connection to the cable modem is 1G, but the actual uplink is 100M down and 10M up.

That means, the queues will be forming on the cable modem (upload) and on the CMTS (download). I do not have control on the queues in either device.

So, what I can do is to limit the upload on my router to 9.9M and download to 99M. Now the upload speed goes something like this: LAN - 1G - router - 9.9M - cable modem - 10M - ISP. Download will go something like this Internet - 10G - CMTS - 100M - cable modem - 1G router - 99M - LAN

This will make upload queue to form on my router. The download queue will mostly form on my router as well, though not fully, but that’s the best I can do.

Then I can run any QoS or queue management on my router.

In practice, I only use priorities for the upload on my backup connection (which is 10M upload), so that browsing goes first and Storj goes last.

On some ISPs I have set up traffic shaping, I use htb and red for that.

---

<div class="post-metadata">

**Author:** ![RecklessD](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/recklessd/32/1130_2.png) [@RecklessD](https://forum.storj.io/u/RecklessD)\
**Post date:** [October 2, 2025, 8:22am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/18 "2025-10-02T08:22:09Z")

</div>

> [@Pentium100](#):
>
> So, what I can do is to limit the upload on my router to 9.9M and download to 99M.

For Buffer Bloat - There is little point to limiting your 100M download, if your LAN is 1000M, buffers should not fill - Your LAN can pass packets 10x faster than your WAN.

If your desire is to limit SMTP to 2M, or guarantee Storj 80M, give the Xbox highest priority and/or something else, then yes you may want/need queue/flow management in both directions.

---

<div class="post-metadata">

**Author:** ![Pentium100](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pentium100/32/6082_2.png) [@Pentium100](https://forum.storj.io/u/Pentium100)\
**Post date:** [October 2, 2025, 9:42am UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/19 "2025-10-02T09:42:23Z")

</div>

> [@RecklessD](#):
>
> For Buffer Bloat - There is little point to limiting your 100M download, if your LAN is 1000M, buffers should not fill - Your LAN can pass packets 10x faster than your WAN.

Buffers will fill up in the ISP equipment though. If I, say, am downloading lots of torrents it may saturate the connection, fill the ISP buffers and then I will have problems. By artificially limiting download I make the buffers mostly fill up on my equipment and then can prioritize stuff.  
It is generally not needed on 100M or faster connections though.

---

<div class="post-metadata">

**Author:** ![snorkel](https://storj.bcdn.literatehosting.com/letter_avatar/snorkel/32/6_22734026db12803ebb3e059622ac3534.png) [@snorkel](https://forum.storj.io/u/snorkel)\
**Post date:** [October 2, 2025, 1:50pm UTC](https://forum.storj.io/t/successrate-vs-sqm/30885/20 "2025-10-02T13:50:26Z")

</div>

Another swing to my go-to appliances. After bashing my Synologies, now my Asus routers are targeted too. 😅  
I didn’t saw any SQM mentions in thier interface, only the QoS and bandwidth limiter.

[Next page](https://forum.storj.io/t/successrate-vs-sqm/30885.md?page=2)
