Speed Issue on new install [Synology], 11 MB/s

[lgriffin]

So I upgraded to a new Synology NAS running DSM 7.2 and installed via the synocommunity version 4.3.2 which requires Python 3.11 as a dependency (3.11.5-8). My old NAS had Sabnzbd with identical configuration and a much older version of Python.

My new install is capping at exactly 11.2Mb/s on multiple different downloads including the test downloads.

Used cache 21.2 MB (31 articles)
System load 0.60 | 0.89 | 0.68 | V=2536M R=200M
System performance (Pystone) 247856 AMD Ryzen Embedded R1600 AVX2
Download folder speed 95.5 MB/s /volume1/@appdata/sabnzbd/@shared_folder@/incomplete
Complete folder speed 118.3 MB/s /volume1/@appdata/sabnzbd/@shared_folder@/complete
Internet Bandwidth 6.31 MB/s 50.48 Mbps

I have plugged my old NAS into the identical network port, identical settings file and I'm getting between 85-90Mb/s consistently. File transfer on the NAS to my desktop is super fast (didn't benchmark, but I moved several Gb of files) and several wgets when ssh'd in similarly gave me the throughout I expect.

After lots of searching I found a similar thread (i can't post links) that pointed to the Python version being the culprit. Before I go down the route of running this in a container and playing around with Python versions to hit the sweet spot has anyone:

- An idea of what configuration changes I could try that I'm not seeing?
- A known version of Python that could work?
- A means to install sabnzbd from the community package and point to said version. If I try uninstall 3.11 it wants to uninstall sabnzbd as well.

Many thanks in advance!

Thread link I can't post is below, just append to the main URL t=25136&sid=b461bac2356067f942624acf0509ede4&start=15

[sander]

> My new install is capping at exactly 11.2Mb/s on multiple different downloads including the test downloads.

Please be precise: 11.2 MB/s (or 11.2 Mbps). So capital B or small b? Big difference, see https://sabnzbd.org/wiki/faq#toc31

Assuming you mean 11.2 MB/s (so: big B): that's 100 Mbps, so Fast Ethernet. Check ethernet port, cable, switch, etc

Nothing to do with python version

[lgriffin]

My apologies, posting on mobile changed the capitalisation it's 11.2MB/s as you have deduced. I have speed tests on my desktop and from within the NAS showing a consistent line speed of 980-990Mbps. Both are connected to the same switch and as mentioned my older NAS with sabnzbd is pulling down at a rate consistent with the line speed available. I swapped the active ethernet ports on the new system just to see would it make a difference and unfortunately it's still capping.

What makes you think it's not the Python version? I'm seeing a lot of github issues, threads on this forum and on reddit that have similar experiences due to Python versions. I'm going to try an uninstall and downgrade the Python version to the other 3.11 variant synocommunity has to see if it changes things. I'm at a loss for what else it could be and if the above doesn't work I'm going to go down the docker route this week to play with the version matrix of Python where I have more control and see if it makes a difference. If I do narrow it down to Python I'll try and diff the change logs to see what could be causing it.

[safihre]

It's not python. I make the SynoCommunity package, it's the same for all Synology users. It works the way it should.

Pause the downloading and refresh the statistics.
The Internet Bandwidth result is super low.. So I'm on Sander with this one a out the 100Mbps thing. Might also something DSM is doing.

[sander]

Seeing is believing.

So, lgriffin, you can try a different python version, but
1) might be difficult/dangerous and
2) safihre and I don't expect any difference. Also because your "System performance (Pystone) 247856" is very nice. And that is a python measurement, so your python is good.

> from within the NAS showing a consistent line speed of 980-990Mbps

Which tool and measurement method do you use on the NAS to measure that Internet speed? Wait: is it Internet speed, or internal LAN speed?
Possibilities:
1) you have multiple network interfaces configured on your NAS (dual ethernet, or ethernet and wifi)
2) your router is limiting the Internet speed for your NAS
3) your measurement is incorrect


If you don't trust SAB's Internet speed measurement result: you can verify with curl / wget / iperf3 from your NAS itself to Internet. I can't help how to install curl / wget / iperf3 on your Synology. But if you can, I can help you with the measurements.
Note: SAB can't be wrong about the Internet speed measurement. It even measures my 2500 Mbps Internet speed correctly. ;-)

[lgriffin]

So I done an uninstall (and settings removal) and reinstall and the speeds are now what I expect them to be. I didn't change anything config / setting wise 2nd time around but this is now resolved. Internally I use the speedtest CLI from speedtest(dot)net which was a helpful step in my own troubleshooting. Thanks for the engagement and guidance here, it was much appreciated.

[sander]

That is weird, but good news.

So what Internet does SABnzbd now report in the Status window?

[lgriffin]

Current stats:
Used cache 0 B (0 articles)
System load 0.04 | 0.16 | 0.16 | V=2469M R=81M
Download speed limited by Disk speed (26x)
System performance (Pystone) 268155 AMD Ryzen Embedded R1600 AVX2
Download folder speed 104.5 MB/s /volume1/downloads/incomplete
Complete folder speed 143.1 MB/s /volume1/downloads/complete
Internet Bandwidth 108.71 MB/s 869.68 Mbps

Only change from above is the folder locations (I literally just clicked defaults when I reinstalled) and there's now a line about download speed limited by disk speed which I don't recall seeing previously.

The internet bandwidth is reflective of my line speed and where I'd expect to see it with a few devices streaming Netflix at the moment in our house. Desktop and NAS on the same switch were broadly at that point earlier today as well (910Mbps and 920Mbps respectfully) and during the day it's as close to the advertised gigabit that I pay for.

Either way I'm happy it has resolved itself but annoyed it's not something that can help others with outside of the "switch it off and on again" approach of reinstall

[sander]

"switch it off and on again" ... maybe we should've started with that ... /s