Question about verification

[kallek]

I really like the new Sabnzbd, but it is one thing that is bugging me. If I download something that fails quick check it is:
1. Verified
2. Downloads par files
3. Verified Again
4. Repaired

Since it has already failed quick check, isn't it possible to just
1. Download par files
2. Verify
3. Repair

This would really speed up the download process since the verification can take a long time. Or am I missing something?

[shypike]

I see your point.
However SABnzbd is designed to do the minimum amount of par2 downloading.
QuickCheck doesn't tell how much par2 blocks are required
(if it did, it would become just as slow as par2-verify).
The extra verification run is needed to determine the amount of required blocks.

Now I do realize that for some it takes less time to download just all par2 files
than doing an extra verification run (it does for me).
But many of our users have download quota or pay-per-MB schemas and will prefer the current method.

Maybe later we'll implement an "optimize for speed" vs. "optimize for minimum MB" option.

[kallek]

Thanks for the reply. It would be great with a "optimize for speed" option.  When downloading a job that is 50 gb it takes a couple of minutes to download all par files while it takes half an hour to verify.

[shypike]

Keep in mind that repairing can take much much longer than half an hour.
It's very well possible that the repair time dwarfs the verification time.