Printable View
I've got a slow upload, using CAMEL I get 300 kB/s using 2 connections to AW-EU
and I get 450 kB/s (MAXED out) using 2 connection to AW-US
I wish I could just FTP my stuff over to a box that will auto post it. My slow uploading breaks apart my releases on the auto indexers in a weird way sometimes.
Assuming that you are posting under a unique username, search engines should compile and display it correctly. I've sometimes had the opposite problem when searching for a download: the site erroneously combines releases made weeks or months apart.Quote:
Originally Posted by mjmacky
Giganews newest feature - a "cyberlocker" - might actually be a useful addition if it provided a mechanism so it could act as a usenet "seedbox" and serve as a kind of 'storage pen' between Giganews usenet servers and people's computers. That's my biggest complaint about uploading to usenet, and a reason why I don't do more: it's easy to get messed up and post corrupt/incomplete articles due to poor line conditions or whatever reason, as NNTP (which was never even designed for posting files) does not have good error-correction built-in. I'd also like the ability to upload to a remote FTP-like server which can check for completeness/errors, before finally posting to NNTP.
Another binary uploader that you might find worth trying out is Usenet Explorer. The free 14-day trial version has no time limit on posting.
Nowhere within 2000miles of me is any provider, including what's left of FIOS, offers upload speeds to consumers that fast, so... :w00t: The few that offers ethernet service do, but you have to be sitting down clutching some nitro pills when they give you the quote.Quote:
Originally Posted by Hypatia
But, I have my poorest machine doing duty uploading, 2.8Ghz Athlon64 single core, 2.5G ram, no problem whatsoever, barley notices when I 'add' a 50GB file (maybe 3 secs of 100% cpu), doesn't slow down the uploading it's doing at all. Maximum ram used when running, <300Mb, cpu at 2-5% avg. w/ posting speed at a bit under 5Mb/s (550MB/s).
Well, works for me. Like to 'try' it at 50Mb/s. Considering that until this last year the maximum available in my area (non-FIOS) was 10by2Mb/s, and FIOS topped out at 25Mb/s upload before they (Frontier Communications) started raising rates through the roof and then shutting things down.
OK, next time around I'm sticking with Camel PP, jbinup is completely fucking up this post. I don't know if it's an issue on the program side or Astraweb side but I've never had these problems while using CPP. This would also be the first time using SSL.
Using AW ssl-eu address. Using 4 of my 50 connections. UL speeds dropping well below 100 kB/s (when it started it was 350 - 400 kB/s).
Pausing midpost, switching server to non-ssl, non-eu server doesn't seem to be helping too much either. I was getting a bunch of these errors:
Code:Error no. 1. occured in part REDACTED ! Details:
One Connection to Astraweb-3 blocked for 15 Seconds .
Error message: Error in method 'Senden': Connection reset by peer: socket write error
Error no. 1. occured in part REDACTED ! Details:
One Connection to Astraweb-1 blocked for 15 Seconds .
Error message: Error in method 'Senden': Connection reset by peer: socket write error
Error no. 1. occured in part REDACTED ! Details:
One Connection to Astraweb-3 blocked for 15 Seconds .
Error message: Error in method 'Senden': Connection reset by peer: socket write error
Absolutely about as next to zero problems here as it can be, posting with JBinUp on Astraweb/US, I monitor post/propagation to Giga and Blocknews at a minimum, usually a third if I see any wobbliness at all (maybe once a month if that, one block error per on one of the two 'biggies'), right now I'm going on three months without a single error either posting or in propagation.... damn near flawless over 2TB+. Back in the DSL days, that would have been at least a year without a single 'wobble'.
Of course, SSL-US plant, 8 connections works fine for that (5Mb/s) speed. When d/l'ing, it takes a full 20 connections to 'flood out' the 22Mb/s connection, but SABnzbd+ is solid as a rock there on a 2core 3.2Ghz Athlon there.
I don't know why you'd be having so many problems with it. I'll presume you are using the latest build that's been around for forever at this point, 0.90 Beta 8 Build 738. I know they had tons of problems with JBinUp and Astraweb in the very beginning, due to the way Astra does their message ID's. But that was a LONG time ago now. It's as solid as granite here....
Well I ended up having ~ 260 missing parts by the end of it. It took awhile to post as the speeds kept choking. I do have the latest build, but am I missing some settings, like check headers with server, etc.?Quote:
Originally Posted by Beck38
The other thing I notice is that jbinup works differently than CPP in that with CPP if you specify 4 connections, it'll use 4 connections for 4 threads. But with Jbinup, 4 connections on one thread is what you'll get. Maybe I just need to specify more connections, I'm trying to repost to fix errors now, what a fucking mess of a post.
I've noticed that on all the old binary usenet clients, each rar file gets one connection ... while on the newer clients, each article -sequentially- gets one connection regardless of which rar the article corresponds to. So as a result, the first rar is completed before the next rar starts.Quote:
Originally Posted by mjmacky
I've discovered that under poor line conditions, the more connections I use, the more errors I end up with. So in those situations of rampant errors, I try to use only one connection, even though it takes much longer.
SSL can also create additional errors under poor line conditions (such as if the 'handshake' procedure gets interrupted) so I disable SSL.
Judging by my experience ( and i post A LOT) i'd say that posting via properly configured Jbinup is safer than posting via any other uploading software like camelsystem\powerpost 52 connections\ easy usenet uploader in terms of getitng incompletes after one's upload process is finished
i have no idea why..
yesterday i had some problems uploading via Astraweb and though camelsystem uploaded at almost full speed many parts got screwed up. Jbinup ,despite of having some strange speed flactuations sometimes dropping to almost zero during that period. managed to finish the same upload OK though it took AW's servers some time to properly process it.
JBinUp one has the option to check headers either with the server one is posting to (standard) or an alternate server, like if one is posting to Astra and doing 'checks' on Giga, something like that. In that configuration, one is really checking the headers PLUS propagation. I checked out that feature when I originally trying the program out, but decided that using the 'standard' of doing header checks on the posting server was 'good enough' as I routinely do manual propagation checks on multiple other providers 'just for grins' so to speak.Quote:
Originally Posted by mjmacky
BTW, I run at around 90% duty cycle upstream, some 20GB/day on average, so it's not the huge jaw-dropping rates others have, I doubt I'd be able to collect and properly process much more than I already am, but JBinUp chugs along with nary a whimper. As far as Astra, I do note the occasional hiccup where the connections get 'reset' at the server (couple of times every 24 hours or so), but JBinUp has handles it just fine.
Hope you get better luck with the configuration and operation...
So should I just chalk it up as having Astraweb glitches? When I review it, the SSL connections gave me MANY more errors than the non SSL connections (same # of conn. = 4). This is the most botched job I have ever seen, and I had to repost a lot of parts that came back as missing. Worse than that, there are some parts being reported by NZBIndex and binsearch as OK, but when I DL them and par2 check, there are missing parts not being reported by the indexers. I don't think I could have had a worse experience with Jbinup.
Now since I'm not the one to just bitch and complain, before I completely ditch jbinup, could you glance over my settings and tell me if there's anything I screwed up here?
http://thumbnails39.imagebam.com/130...5130672774.jpg http://thumbnails12.imagebam.com/130...f130672775.jpg http://thumbnails30.imagebam.com/130...8130672777.jpg
http://thumbnails28.imagebam.com/130...1130672779.jpg http://thumbnails27.imagebam.com/130...c130672781.jpg