News Server DL using much more Data than it should

S

schpat

Well-Known Member
Joined
Jan 6, 2006
Messages
135
Reaction score
0
Hi All,

I'm a bit new to the whole NZB thing, I've been dabbling for a year or so, but now I've decided to make it my main means of DL. The problem is that it seems that there is a lot of data being wasted.

I am currently using SABnzbd to DL files because it is good at unpacking and sorting. After a file is finished you can see how much data it actually took to DL in the history section. Files that should be less that 200MB are taking an average of 850MB to DL and more importantly much more time than they should.

I'm hoping that this is a problem with my settings or something.

This is my setup

ISP:
Mweb uncapped 384K (waiting for an upgrade)
News servers:
Mweb and Thundernews
Connection Speed to Servers;
on average about 20kB/s

Is this actually normal? Has anyone got any ideas about what I can do?

Thanks
 
And this happens with all nzbs? I've had an issue where some of the files are indexed more than once in the nzb but it's very rare.

Are you measuring the total downloaded amount with another tool (like Netlimiter) and what size does SABnzbd report for the nzb before its completed?
 
Remember, don't download the PARs. Only download enough PAR blocks to repair the download if it is damaged.

You do have QuickPar installed (or Multipar perhaps), don't you?
 
I don't think SABnzbd+ gives you the option to not download the PAR files?
I've just looked at my SABnzbd+ setup, and I can't find an option like that, unless it only downloads the PAR files when needed.

You should also configure SABnzbd+ such that it doesn't download the sample files.
 
SABnzbd only downloads the PAR files it needs. It starts by downloading all normal files and the smallest par. If the files don't pass our QuickCheck function, we run a full par2 verification. Once SABnzbd determines how many files are broken or missing it will go back and intelligently download only however many pars it needs and repair.
 
I think what most people don't realize, is the overhead there is on usenet, so you are essentially downloading more data than the actual size of the files. It works a lot like emails, where the binary data is base64 encoded into a text message.

NB. These numbers are for explanation sake, and not 100% accurate!

Let's say you are downloading a 300mbyte clip. You will probably end up downloading anywhere between 350-400mbyte, which excludes any .PAR/.PAR2 files.

According to wikipedia, the overhead is +- 33% !!

Link: http://en.wikipedia.org/wiki/Base64
 
Tinuva said:
I think what most people don't realize, is the overhead there is on usenet, so you are essentially downloading more data than the actual size of the files. It works a lot like emails, where the binary data is base64 encoded into a text message.

NB. These numbers are for explanation sake, and not 100% accurate!

Let's say you are downloading a 300mbyte clip. You will probably end up downloading anywhere between 350-400mbyte, which excludes any .PAR/.PAR2 files.

According to wikipedia, the overhead is +- 33% !!

Link: http://en.wikipedia.org/wiki/Base64
Click to expand...

Better than a Torrent where the overhead can be as much as 100% :p
 
Tinuva said:
I think what most people don't realize, is the overhead there is on usenet, so you are essentially downloading more data than the actual size of the files. It works a lot like emails, where the binary data is base64 encoded into a text message.

NB. These numbers are for explanation sake, and not 100% accurate!

Let's say you are downloading a 300mbyte clip. You will probably end up downloading anywhere between 350-400mbyte, which excludes any .PAR/.PAR2 files.

According to wikipedia, the overhead is +- 33% !!

Link: http://en.wikipedia.org/wiki/Base64
Click to expand...

Yes, this is true but the OP said a 200MB file was downloading 850MB - that's slightly more than 33% :)
 
Tinuva said:
I think what most people don't realize, is the overhead there is on usenet, so you are essentially downloading more data than the actual size of the files. It works a lot like emails, where the binary data is base64 encoded into a text message.

NB. These numbers are for explanation sake, and not 100% accurate!

Let's say you are downloading a 300mbyte clip. You will probably end up downloading anywhere between 350-400mbyte, which excludes any .PAR/.PAR2 files.

According to wikipedia, the overhead is +- 33% !!

Link: http://en.wikipedia.org/wiki/Base64
Click to expand...
This definitely used to be the case, but most Usenet binaries are encoded with yEnc these days. yEnc's overhead is about 1-2%.
 
Been using SABnzb for years now and never had this issue...
SABnzb will also only download pars if it needs it.

Maybe your little brother is downloading porn on the skelm and then deleting the history from SABnzb?
;)
 
Tinuva said:
I think what most people don't realize, is the overhead there is on usenet, so you are essentially downloading more data than the actual size of the files. It works a lot like emails, where the binary data is base64 encoded into a text message.

NB. These numbers are for explanation sake, and not 100% accurate!

Let's say you are downloading a 300mbyte clip. You will probably end up downloading anywhere between 350-400mbyte, which excludes any .PAR/.PAR2 files.

According to wikipedia, the overhead is +- 33% !!

Link: http://en.wikipedia.org/wiki/Base64
Click to expand...

Actually they don't use base64 anymore but rather yEnc which has far less overhead.
 
If anyone is DL'ing pron they had better share!!

Thanks for everyone having a look at this for me. The news thing seems so much more civilised than torrents, but with this kind of ovrhead it just doesn't seem right. I'm reading the 850MB from SAB History

Maybe I'm reading the info incorrectly but to my mind it shouldn't take 13hrs to dl a 190MB thing. Here is screen cap so you can see what I mean:

http://postimage.org/image/2d242vd44/
 
Something very weird there. No ways that BBT or The Office would be 800mb. Those are not even 720p versions.
 
I suspect you nzb file has other junk added into it, get it from somewhere else and compare.
 
I'm getting them from NZBrUS, because they have an rss feed that is customisable and easy to use. How can I see if the nzb has junk in it? In the queue it only reports 190MB
 
Setup the .nzb Backup Folder under Folders, and then set Detect Duplicate Downloads to Discard or Pause under Switches - all in SABnzbd+.
If it said the size is 190MB, then it would've only downloaded 190MB, unless they re-issued the same episode a few times, in which case your SABnzbd+ would've downloaded the same episode a few times.
For this reason I prefer to use my own download script that searches on NZBMatrix.com. It only downloads the episode once, and if the episode had a fault, I just go and manually download the correct one.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X