Sonarr took care of post-processing and sorting because I kept finding the scripts finicky and often not working at all (a problem I never had with sabnzb+). (Surprisingly, though, it barely uses any resources. It was a nightmare if it had 20 in the queue. Even with just one thing downloading, I found the main UI slow to respond. I started out with sabnzb+ and even though it had a lot going for it in terms of a lot of good config options. As some others have alluded to, the grass isn't always greener on the other side.
Nzbget vs sabnzbd 2017 software#
So no, you aren't really missing out on any big features (provided you're using the most recent SABnzbd alpha release) and if you're happy with your software then there is no reason to switch. I also find that SAB is more widely supported from an integration standpoint. I personally like the postprocessing capabilities of SAB better and I dislike the history management of NZBget. For most computers built in the last 4-5 years you'd be hard pressed to find much difference in performance.
Nzbget vs sabnzbd 2017 download#
This would only impact download speed and would have no benefit for par repair or decompression actions. NZBget should be lower on resources but that only matters on low powered devices such as you NAS and some other SoC or APU powered devices. SABnzbd now supports failed download handling and server priorities (as of 8.0alpha2) amongst other features. There used to be a feature gap between the two but in some recent releases (and alpha releases) SABnzbd has bridged that gap.
Are there some major features I'm missing here? Or do most people just truly get faster speeds with NZBget (which isn't really an issue for me). So, for me, at the end of the day, these two seem pretty similar and it doesn't seem like a necessity to change over to NZBget. If a download fails in NZBget I don't see it giving as much information as SABnzbd. With SABnzbd you can click a "check all", pick the category, and hit "apply all". I'm sure with some more tweaking I could get NZBget to do a better job of auto-categorizing files (so that they sort properly when finished), but what about for stuff that doesn't auto-categorize? It's kind of lame having to click each download to bring up a pop-up menu to categorize them.
I installed the Videosort plugin which helps, but even after some experimenting/testing I haven't found it to work quite as well as SABnzbd's native system. In terms of unpacking content I haven't timed them side by side, by I don't notice a substantially quicker unpacking in NZBget.įor sorting, NZBget has very little in the way of built in options. I'm running these on a Synology DS1010+ and I don't see many advantages to NZBget so far. I have been a long time SAB user and recently installed NZBget to see how it compares.
Nzbget vs sabnzbd 2017 full#
Now, I know the RPi 2 isn't a powerful device and I can't expect a full 100Mbit/s (my internet connection).Looking for some input as to why so many people seem to prefer NZBget over SABnzbd. I've read the performance tips and tried various changes (number of connections, cache, articles size etc) but seeing no difference. The external hard drive is showing no problems either as I'm able to transfer files to it over FTP and get good speeds locally while using usenet (for testing purposes). While I get between 4-6MB/s using SN, I only get 2MB/s using NZBGet.ĬPU and RAM is only at about 40-50% (high is 70% but rarely). My problem however is that NZBGet performs about 50% of what SABNzbd does in terms of download speed. I've moved from SABNzbd to NZBGet because I heard that NG offers better performance, especially when it comes to devices such as the RPi 2.