newsbin.com

Quick-turn release for Version 6.20 Beta 3. Fixes two issues:

• Hooked up Duplicate Detection again.
• All Confirmation Windows default to on now. You can turn them off under Options/Confirmation Windows.

Download link is on the Newsbin Beta Page.

Any issues with this release, please reply to this thread, contact us through our Technical Support Form or swing by our irc channel - #newsbin on irc.newsbin.com.

i checked NB's test downloads feature and it works kinda strange (that is if it is not its intended behaviour) if i have fill server enabled


1) Fill server is enabled (no header + fill server ON)

log shows 17 "post not found" errors yet NB says that the release is 100% complete all blocks are there

2) Fill server OFF
99% completion and 17 blocks are not found

3)nzb download checker
Files found: 81
Message-ID's required: 31222
Message-ID's found: 31222
Message-ID's missing from the NZB: 0 (0%)
The files were posted 307 day(s) ago.

Parts checked: 31222
Undownloadable parts: 17


Is it intended? it is kinda confusing, imho
Mixing the results from the main server and the fill one. Well it gives the whole picture whether one could get a particular release having all those servers enabled, but if i want to check availability of something on the main server i have to turn off completely all fill servers.

I hear what you're saying but, I'm not sure why it's an issue. Isn't that WHY you have a fill server in the first place? The test feature shows what you can download with your current server setting.

no its not an issue, i guess, i just wanted to get a clarification about the whole idea.
thanx
btw is it possible to utilize more than one connection for checking?

If it's not already, it's a bug, it should be using all connections no differently than a file download.

Quade wrote:If it's not already, it's a bug, it should be using all connections no differently than a file download.

my mistake. the speed is very slow max 1+Mbyte(best case) so i thought it was using just one connection.

In "Testing" the amount of data transferred is small compared to downloading the complete chunk. That means the time delay of sending the commands to the server has far more impact. Normally it's

command
600k
command
600k

and the other threads are doing the same thing. With testing it's:

command
4k
command
4k

So, the delay in sending the command dominates.

what does this error mean?

[04:51:31] ERROR - MF_AssembleFileUtil - Thread Crash
[04:51:31] ERROR - INT_AssembleFile: Assembly Failed 2SUUT4EVDKDSRBN[09/83] - "2SUUT4EVDKDSRBN.part08.rar" yEnc

it seems Nb has stopped writing to disk or whatever(when cache decreases)

part size is large - 300mb when it is written cache is at zero
i restarted NB and it "lost" several last downloaded parts which were downloaded when these errors starting popping up and started redownloading them.

viewtopic.php?f=43&t=29309&hilit=%2F3gb

I'd set the cache to 100 or something and then set the /3gb switch. Honestly with your machine, if this continues to happen I might set the "MemCacheLimit" to zero too.

thanx
Interestingly enough, sabnzbd with Article Cache Limit 300Mb managed to maintain 5.9-6Mbyte speed throughout the whole download process of this item(writing to disk and downloading, usin' no more than 330Mb ram)..i wonder what 's so different about Nb and sab ans why sab core 2 duo 3ghz,4 gb ram(3.5 available) is enough for sab and is not enough for NB.. just curious

oh well.. i'll try it =) thanx anyways.

PS please dont consider that as bitching or whatever. it just really bothers me.. i love NB..

Speed Limiter is completely off at my PC for this version.
Didn't work great with the previous versions, but now it's completely wrong
Set to 90 Mbps leads to a speed around 9 Mbps.

It's not the amount of RAM. It's the amount of address space. The /3gb switch gives you an additional Gig of address space. It means you can memory map larger files. Memory mapping is the fastest way to scan for PAR blocks.

Dreamland wrote:Speed Limiter is completely off at my PC for this version.
Didn't work great with the previous versions, but now it's completely wrong
Set to 90 Mbps leads to a speed around 9 Mbps.

I'm experiencing this issue, as well. In 6.1, the speed limiter actually worked quite well for me (within 1Mbps of the selected value), but in this version, it just seems to result in a random value somewhere below the selected limit. It seems to fluctuate between 30-50% of the speed limit I set in the options, but even that isn't entirely consistent.

Everything else is working well for me with this build, though.

I'm working on the speed limiter today. It's a real thorn in my side.