Quote:
Originally Posted by zinglebarb
If your downloading zips bigger than 255 meg then you need a multi The Zip manager being slow is a known fault with Easynews.
|
I downloaded full speed no problems with 5 threads once routing fixed as per first post (only 2M line thhough)
Quote:
Originally Posted by zinglebarb
If your downloading zips bigger than 255 meg then you need a multi threading download manager anyway as transparent proxies are known to damage the zips
|
I've not had any damage here downloading 2G zips via port 81. NTL Bromley. Why would multi-threading prevent damage? Avoiding the proxy would - hence port 81.
Lordy
---------- Post added at 14:50 ---------- Previous post was at 14:48 ----------
Quote:
Originally Posted by Sahil
For those of you who use Easynews etc, does your Card get billed in USD? or GBP? I would like to try out easynews, which is why Im asking.
|
Just like when you go on holiday. Your bill will show the UK Sterling equivalent of $10 using CC companies exchange rate. (around £6 ish)
Lordy
---------- Post added at 15:23 ---------- Previous post was at 14:50 ----------
Quote:
Originally Posted by Horace
It doesn't help that much since NTL seem to be throttling connections to Easynews.
|
Route
is something to be considered and it helps a
lot if your route is not already optimal. I had 5 threads on the go yesterday (via port 81) and it was downloading at between 80and 150Kbps.. as soon as I fixed my route (as per OP) it went up to 238Kbps solid. So it certainly helped me.
It's certainly worth looking at, as people could be assuming its NTL being sneaky when fixing their route would certainly help towards to goal of faster downloads.
I just posted because I realised all my previous attempts to change the route, were invalid because they were done from the port 80 admin page.
I suggest people do all of the following:
- try changing their route (via
http://members.easynews.com:81/route/) ,
- for HTTP use port 81,
- and use multiple threads.
- (and IMO use HTTP anyway as it will be faster all else being equal - less to download)
Quote:
Originally Posted by Horace
Making multiple connections either in an NNTP app or in a download manager (FDM) if downloading via the web interface are the only ways I've found of getting around this.
|
Remember Easynews is in the States, so
latency is likely the issue (not NTL being sneaky).
People forget that NNTP downloads from a decent newsreader, often implicity have multiple connections at the same time (as 'n' .rar parts are downloaded concurrently), then they compare that to a single thread on HTTP(via NTL proxy) and say NNTP is faster!
When using HTTP they should also use whetever mechanism also allows multiple connections.. AND use port 81.. and they will be no real problems.
To get a full bandwidth download with a single connection (at the TCP/IP level) of any protocol (NNTP or HTTP) from across the pond .. is wishful thinking... because the latency is higher and network congestion could be anywhere..
Ping a site in the UK and then ping one in the US. Thats the reason why you use multiple threads whether it be NNTP or HTTP.
But for HTTP definitely use port 81!
Also regarding NTL throttling traffic...
Looking at my trace times from Easynews to NTL, I couldn't see any evidence of that.
Code:
HOST LOSS RCVD SENT BEST AVG WORST
ge1-8-1000m.sw1.easynews.com 0% 10 10 0.40 0.90 2.36
e-2-2-1000m.core-03.phx1.puregig.net 0% 10 10 0.28 0.38 0.54
65.118.182.93 0% 10 10 0.77 4.25 32.84
205.171.129.113 0% 10 10 1.32 3.49 11.83
67.14.10.54 0% 10 10 11.73 19.71 47.05
205.171.213.110 0% 10 10 11.96 25.53 109.08
205.171.1.58 0% 10 10 10.90 16.18 59.16
po12-0.ashcr1.Ashburn.opentransit.net 0% 10 10 65.75 67.00 68.27
po6-0.loncr3.London.opentransit.net 0% 10 10 134.94 136.91 141.83
so-1-0-0-0.loncr4.London.opentransit.net 0% 10 10 135.18 142.18 185.46
??? 100% 0 10 0.00 0.00 0.00
nth-bb-b-ae0-0.inet.ntl.com 0% 10 10 138.44 141.00 153.70
pop-bb-a-so-100-0.inet.ntl.com 0% 10 10 138.10 147.63 216.17
brom-t2core-a-pos31.inet.ntl.com 0% 10 10 139.23 189.23 353.65
lwhm-t2cam1-a-ge-wan31.inet.ntl.com 0% 10 10 139.09 144.75 176.33
ubr05lewi-ge10.inet.ntl.com 0% 10 10 140.12 145.36 181.69
??? 100% 0 10 0.00 0.00 0.00
The big drop is across opentransit.net which I suspect is crossing the pond.
Its simply the distance involved, hence multiple threads to alleviate latency issues.
Lordy