Unpack Questions
Posted: October 2nd, 2024, 2:17 am
New user here looking to optimize unpacking in a NAS scenario.
SABnzbd runs in a VM with an SSD scratch disk for 'incomplete' items. Items get imported and marked by Sonarr/Radarr with their respective category, which points that category to the final destination on a NAS with spinning disks.
It seems the VM and SSD is unpacking direct to the NAS. Should the unpacking be done on the SSD and the unpacked files copied to the NAS?
When I run the benchmark tool within SABnzbd, it shows 3.3MB/s for the complete folder when pointing to the NAS. When I change this to the SSD, it shows 924.2 MB/s. Obviously there will be a huge difference but 3.3MB/s is concerning.
Per their wiki, I disabled 'direct unpack' and 'pause downloading during post-processing'. I tested direct unpack to see if it is actually unpacking to the SSD before it is finishes, but it unpacks to the NAS final destination.
My end goal is to alleviate any additional strain on the NAS and ensure this process works as fast as possible.
TIA.
SABnzbd runs in a VM with an SSD scratch disk for 'incomplete' items. Items get imported and marked by Sonarr/Radarr with their respective category, which points that category to the final destination on a NAS with spinning disks.
It seems the VM and SSD is unpacking direct to the NAS. Should the unpacking be done on the SSD and the unpacked files copied to the NAS?
When I run the benchmark tool within SABnzbd, it shows 3.3MB/s for the complete folder when pointing to the NAS. When I change this to the SSD, it shows 924.2 MB/s. Obviously there will be a huge difference but 3.3MB/s is concerning.
Per their wiki, I disabled 'direct unpack' and 'pause downloading during post-processing'. I tested direct unpack to see if it is actually unpacking to the SSD before it is finishes, but it unpacks to the NAS final destination.
My end goal is to alleviate any additional strain on the NAS and ensure this process works as fast as possible.
TIA.