SABnzbd Forums

Dear Sabnzbd users,

I had some performance problems with sabnzbd downloading on my 1.5 TB SATA media drive. Because the parring and unpacking is pretty intensive disk usage I decided to add (another) 15K SCSI drive in my server to use as sabnzbd parring /temp drive so it would not interfere with (a lot of) people streaming media of my media drive via SMB. The only problem is that sabnzbd doesn't have an option to specify an unpacking directory but only the cache and temp folder for parring and repairing so my problem wasn't solved this way.

I'm looking for a solution to do all the parring repairing and unpacking  on the 15K SCSI drive and then move it to final destination so people won't notice when watching/listening my media. I searched around on the forum and found someone who uses robocopy in a cronjob to watch a temp directory to complete unpacking and then move it to the final destination. But I don't think that's a clean solution because I have around 15 categories in sabnzbd that need to be watched by different crons when using this method. I was wondering if anyone else knows a better solution to this problem.

Edit: I'm running on a Windows 2003 RC2 server by the way.

Cheers,

XiS

XiS wrote: that sabnzbd doesn't have an option to specify an unpacking directory

I don't understand your problem.
You cat set separate folders for the cache, for the temporary download folder and for each category.
So you can always unpack from one drive to another.

Sorry For my very late reply. But I'm trying to say that you can't do the unpacking action on drive X and after unpacking moving it to Drive Y

SABnzbd is designed to unpack from the temporary to the final folder.
These can be on the same drive or on different drives.

When you want to download and unpack on the same drive, that's possible.
If you want to move the end result to a different drive, you need to write your own user script.

Thanks for your fast reply. I guess is i'll have to create my own script. But I wonder if a 'normal' copy will be different in terms of I/O (random/sequential) on the destination disk to the unpack method. Cause for some reason streams are stuttering when sabnzbd is unpacking to destination disk.

It's unrar that does the unpacking and it is very capable of saturating the disk channel.
Unlike Linux, Windows doesn't have the ionice utility.
I have a similar problem with my WHS box.
So I never download in the evenings.

Hmm, yea. Yet another reason why I should make the switch to linux. Well thanks for your help. Maybe this is going to be the decisive argument for me to switch to linux, or, maybe I'll just make a script to copy it at a slow rate.

Thanks again.

XiS