Thanks for getting back to me, yes i did figure out that the link was strictly source code and not what I needed, I will wait then to see if he comes up with a fix for this, at least i think i now know it is not the provider and I will put that fight aside for a bit.

Has any progress been made on trying to figure out if it is SABNZBD or the provider that is dropping speed during the downloads, need to figure out which one it as I don't like paying for 1gig download speed if they can't sustain it or should i look for another usenet client software.

I use a mac and write directly to the internal drive and transfer to the NAS drive after the download is finished. I would be more than willing to help with testing if you have a version for the mac you want to try.

whitlee: your problem is completly different than saintnick. His problem is regarding running SABnzbd on the NAS and not on the desktop machine.

It is also not version related but more likely to be network I/O related. Have you tried what happens when you download with your Complete folder locally?
You should also try setting your download speed to something in the middle, like 30MB/s and see if it can maintain that.
SABnzbd will unpack while you download, causing a lot of stress on your disks and network.

Well I have been using NZBVortex for the last week and no issues as it downloads at around 110 MB/s with absolutely no, problems so that would seem to tell me that SAB doesn't handle high speed downloads.

Hi Safihre,
I'm back from vacations, and back to consuming work.
I tried all of the 2.3.4 builds, both the two that you link above and the latest at Synocommunity. All give the same behaviour, DL speed collapses after some minutes from just under 20 MB/s to KB/s. Any version of 2.3.4 never gives the 24MB/s flatline max I was used to.
So I tried to install the latest 2.3.1 from Synocommunity, but the installer doesn't allow downgrading.
What can I do now? It seems to me any implementation of the new external SabYenc library of any version of 2.3.4 just doesn't work at all well on these Synology's.

I want to identify if the problem is in the C-code or the Python code.
Thanks!

Safihre, I finally was able to install the version you intended to link to. And the results don't surpise me but will disappoint you.

I immediately got back to my flatline max DL-speed of 200 mb/s, 24,2 MB/s :-) See this graph:

The first part of the graph is the sabnzbd-oldyenc with just three connections (which worked best for your new version with SabYenc). This gave 21-23 MB/s which was already much better. Then I switched to my normal 12 connections, and got back my familiar flatline 24,2MB/s
Also worthy noting is that in my DSM resource monitor, only 52% of memory was consumed, in contrast to before where SabNZBd would push it above 80%.
This is bad news for SabYenc.
Please consider fixing, as I am not alone in this...
If I can be of any assistance, with logs or so, let me know.

I would also like to second the request to fix the issue. I think the problem is with less memory being used, but the developers know better.