December 17, 20169 yr I'm trying to improve the performance during the unpack of NZBGET which is slow when the Mover is running. Unpack times go from 1m to 10minutes when the mover runs and NZBGet is unpacking to the cache drive. The the PP-Queued items start stacking up quickly in NZBGet. All other times this setup runs fine if the mover is not running. I thought about getting a larger cache drive but the mover would still have to run just as much to move the data. Here's my config in sequence of how the data flows: AppData for NZBGet Unassigned Device 1 - 256GB SSD - This is where NZBGet's cache, history and nzbs are stored Inter (Intermediate Directory) NZBGet Unassigned Device 2 - 2TB SSD - This is where all the news articles are assembled into their complete form in .rar files or whatever the content is. Download Destination Array Cache Drive - 512GB SSD - This is where all downloads end up and are post processed by sonnar, couchpotato or other containers. From here the mover runs and transfers to the array. Any thoughts? Should I try unpacking straight to the array and skip the cache drive?
Archived
This topic is now archived and is closed to further replies.