I've set up the main download folder to an ssd, then download folder for downloads to an HDD(used to have this as SSD, but tried this hoping it would fix it, but didnt), and unrar folder to a third HDD.
Quade wrote:1 - I'd probably try the latest 6.73RC
2 - You might want to enable aggressive mode in the autopar options and make sure the retries are only 2
3 - You might want to tell Newsbin to stall the download while unraring and repairing (it's in the performance options). You certainly can download and assemble files are the same time but doing that, particularly on a spinning disk will slow down assembly and scanning the files.
I think it doesn't sound like par speed is the issue. Instead I think the download is getting way ahead of unrar and repair. Having a monsterous cache is not pointless but you hit a point of diminishing returns. I'd probably set it to 1000 or less.
PAR scanning happens as the files are assembled so, while not free, it's not that expensive since the data is already wizzing by for the assembly. I suspect your real issue is trying to download and repair simultaneously. If you connection is really fast, the downloaded chunks will backlog and you'll see them finish assembly well after the download completes.
How fast is "fast" download?I've set up the main download folder to an ssd, then download folder for downloads to an HDD(used to have this as SSD, but tried this hoping it would fix it, but didnt), and unrar folder to a third HDD.
You mention the download folder twice. Best download performance is likely to happen when the data and download folder are on SSD. Then you can set the unrar folder to some other driver, SSD or not. If you're not using a local internal disk for the download path, you're probably crippling unrar and repair performance.
Fast download is gigabit speed so around the speed of 120Mb/s so the limit of a normal hdd
It's just strange that I've not had this problem before, and only seems to happen after the reinstall. I'll also try upgrading to the newer version.
Quade wrote:Fast download is gigabit speed so around the speed of 120Mb/s so the limit of a normal hdd
120 Mb/s isn't particularly fast. 120 MB/s is pretty blazing fast so I think we need to clarify big B or little b. Bytes or bits. If you really are getting 120 MB/s then my "download getting ahead of assembly" theory is probably correct.It's just strange that I've not had this problem before, and only seems to happen after the reinstall. I'll also try upgrading to the newer version.
Ideally all of your downloads will be perfect. If that's the case then PAR processing doesn't actually do anything. On the other hand if you find Newsbin is repairing every download then this will crush your performance. With a decent server(s) and proper reliable setup, you should be getting mostly perfect downloads. If everything has to be repaired, there's a problem somewhere. It sounds like there's a decent amount of repairing going on.
The problem with your theory is though that it hasnt been a problem before, with the same download speeds and the same providers.
Well I'm definitely not getting perfect downloads, most of them need to be somewhat repaired, but all downloads will be par checked first.
I've done everything you said. But it seems to me that it has something to do with the newer builds.
Quade wrote:I've done everything you said. But it seems to me that it has something to do with the newer builds.
Could be lots of things.
Just from your image, I can see these files all show incomplete PAR counts and all show that some files are still downloading. (The DL in the details sections) I'd set it to pause download during unrar and repair and see if your symptoms change.
but it doesn't seem to prioritize to finish the checking before moving on.
Users browsing this forum: Bing [Bot] and 2 guests