Sabnzbd only maxing out at 20MB/s using SSL, 70 without SSL.

[jimbo]

Hi there,

We've been struggling with Sabnzbd for quite a while now and I'm not sure why. We were originally running the following: (github .com/linuxserver/docker-sonarr) and it just maxes out at 20 MB/s. We then decided to reinstall to Windows Server 2016 as it's made to be run on Windows, thinking surely it'll work but again - it's only maxing out at 20 MB/s. I've done a generic write/read test and get 300 MB/s.

It's virtualised using Proxmox KVM and has access to 8 cores, 16 threads. We've been doing some testing and when deactivating SSL - we get up to 70 MB/s but when SSL is enabled, 20 again. The server CPU's are E5620's with 24gb of memory, the CPU supports AES-NI.

Any ideas?

Thanks

[safihre]

You can try lowering the encryption level: https://sabnzbd.org/wiki/advanced/ssl-ciphers

But can also depend on your server. Always worth to get a free trial at some other provider, and make sure to use the server closest to you. So check the domains, maybe there's a dedicated eu/us host.
Also make sure to have memory limit in Sab set to 1G.

SSL is just annoying, because we can only get data in 16KB blocks due to encryption package size, while without SSL we can get 1MB at a time. All the connection switching is just not very optimal.

[safihre]

What if you run it without virtualization or Docker, but directly on the server?

Unfortunately maybe nzbget is (right now) a better solution for high performance environments :/

[jimbo]

You can try lowering the encryption level:

But can also depend on your server. Always worth to get a free trial at some other provider, and make sure to use the server closest to you. So check the domains, maybe there's a dedicated eu/us host.
Also make sure to have memory limit in Sab set to 1G.

SSL is just annoying, because we can only get data in 16KB blocks due to encryption package size, while without SSL we can get 1MB at a time. All the connection switching is just not very optimal.

We are using a server based in the same country as the server and have tried two different providers, the memory limit is something I haven't checked but will do so (I believe this will be maxed out anyways though). It's just odd to be quite honest, unfortunately we aren't able to test it on the main node due to it being used for some other things.

I really don't like NZBGet, wish this worked

[safihre]

Did you try the cipher?

[jimbo]

Did you try the cipher?

Yup, we tried the Cipher. We ended up trying it on the host dedi as you suggested and it ended up downloading at full gbit so this issue appears to be direct with virtualisation.