Giganews Speeds

Ignitionnet · 18-09-2008, 10:42

Was wondering if anyone else had seen some performance issues with Giganews?

No matter how many threads I tried, no matter what I did, last night I couldn't get above 15Mbit.

Also noteworthy was that on my little trace I could see TCP Window adjustments

Switched the NNTP client off, did a speed test an immediately full 20Mbit. Tried the Giganews speed test, 8Mbit.

Anyone else seen this, struggling to think it's an issue with Giganews, it affected both news.giganews and news-europe.

dilli-theclaw · 18-09-2008, 11:18

Maybe you could try using port 80 or 23 for your giganews, just in case.

pk1209 · 18-09-2008, 12:40

I'm on Giganews - can't remember the name, some kind of precious metal (20 connections SSL - unlimited package).

I switched to from Usenetserver in search of better retention, i obviously got that, but as long as i'm not under traffic management it maxes the bandwidth every time. I never got this with Usenetserver, but i was blaming it on VM.

Giganews really is worth the extra $

(no i don't work for them)

Ignitionnet · 18-09-2008, 13:42

Quote:

Originally Posted by Jefferson T

Maybe you could try using port 80 or 23 for your giganews, just in case.

Nah see above I also tried the Giganews (HTTP based) speedtest.

I think more likely it's down to asymmetrical routing and problems along the route, or likely capacity issues on the route as I tried it just after the end of the STM period when people are likely to kick off their downloads. Downside of limiting for part of the day, it just moves the congestion period.

C:\>tracert news-europe.giganews.com

Tracing route to news-europe.giganews.com [216.196.109.144]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 12 ms 11 ms 8 ms 10.183.64.1
3 10 ms 10 ms 9 ms osr01mort-v11.network.virginmedia.net [62.30.60.1]
4 11 ms 12 ms 10 ms osr01croy-tenge73.network.virginmedia.net [62.30.242.41]
5 10 ms 9 ms 12 ms bre-bb-a-ge-300-0.network.virginmedia.net [195.182.178.82]
6 12 ms 13 ms 15 ms nth-bb-b-so-310-0.network.virginmedia.net [212.43.162.218]
7 16 ms 14 ms 14 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
8 20 ms 23 ms 23 ms tge8-1.fr3.lon.llnw.net [87.248.208.129]
9 21 ms 25 ms 20 ms tge7-2.fr3.ams.llnw.net [69.28.171.93]
10 29 ms 20 ms 20 ms ve5.fr4.ams.llnw.net [69.28.172.114]
11 21 ms 20 ms 21 ms giganews.ve210.fr4.ams.llnw.net [87.248.196.6]
12 22 ms * 147 ms 216-196-108-133.ams.giganews.com [216.196.108.133]

Return path:

1 216-196-110-3.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 216-196-108-134.ams.giganews.com (216.196.108.134) 0 ms 0 ms 0 ms
3 amst-ic-1.inet.ntl.com (195.69.144.40) 0 ms 0 ms 0 ms
4 pop-bb-a-as0-0.network.virginmedia.net (213.105.175.5) 10 ms 11 ms 10 ms
5 pop-bb-b-ae0-0.network.virginmedia.net (213.105.174.230) 10 ms 10 ms 11 ms MPLS Label=103680 CoS=0 TTL=0 S=1
6 osr02croy-tenge82.network.virginmedia.net (195.182.178.85) 10 ms 14 ms 10 ms
7 osr01mort-tenge81.network.virginmedia.net (62.30.242.58) 10 ms 10 ms 10 ms MPLS Label=1475 CoS=0 TTL=0 S=1

monkey2468 · 18-09-2008, 17:42

Try using the USA server.

Ignitionnet · 18-09-2008, 18:02

Quote:

Originally Posted by monkey2468

Try using the USA server.

See first post:

Quote:

Anyone else seen this, struggling to think it's an issue with Giganews, it affected both news.giganews and news-europe.

I suspect news.giga has become an anycast address as it routes to Amsterdam also, and is therefore subject to the same asymmetrical routes:

1 1 ms 1 ms 1 ms 192.168.1.1
2 12 ms 8 ms 7 ms 10.183.64.1
3 10 ms 9 ms 9 ms osr01mort-v15.network.virginmedia.net [62.30.242.129]
4 9 ms 9 ms 12 ms osr02croy-tenge73.network.virginmedia.net [62.30.242.57]
5 13 ms 11 ms 11 ms pop-bb-b-ge-210-0.network.virginmedia.net [195.182.178.86]
6 11 ms 19 ms 13 ms pop-bb-a-ae0-0.network.virginmedia.net [213.105.174.229]
7 24 ms 16 ms 13 ms nth-bb-b-as3-0.network.virginmedia.net [213.105.172.13]
8 19 ms 15 ms 14 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
9 27 ms 24 ms 25 ms tge8-1.fr3.lon.llnw.net [87.248.208.129]
10 22 ms 20 ms 19 ms tge7-2.fr3.ams.llnw.net [69.28.171.93]
11 22 ms 20 ms 20 ms ve5.fr4.ams.llnw.net [69.28.172.114]
12 26 ms 21 ms 19 ms giganews.ve212.fr4.ams.llnw.net [87.248.196.14]
13 * * 21 ms 216-196-108-133.ams.giganews.com [216.196.108.133]

etc

Rik · 18-09-2008, 18:44

No problems to report here.
19Mbps (20 Connections WITH SSL (Port 443))

AdamD · 18-09-2008, 19:03

I get the same good speeds here (2.3mb/sec and then 580kb/sec when I'm under traffic management, heh)

Ignitionnet · 18-09-2008, 19:26

Gonna try it again just after STM is cleared at 9pm and see if I see the same issues.

Could you guys who are seeing good performance post a traceroute please?

Rik · 18-09-2008, 21:35

Quote:

Originally Posted by Broadbandings

Gonna try it again just after STM is cleared at 9pm and see if I see the same issues.

Could you guys who are seeing good performance post a traceroute please?

Tracing route to news-europe.giganews.com [216.196.109.144]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms kerberos [192.168.1.1]
2 9 ms 15 ms 7 ms 10.136.220.*
3 30 ms 8 ms 7 ms lutn-t2cam1-b-v108.network.virginmedia.net [80.4.118.221]
4 18 ms 7 ms 7 ms lutn-t3core-1b-ae2-0.network.virginmedia.net [195.182.174.193]
5 10 ms 7 ms 7 ms nth-bb-b-so-120-0.network.virginmedia.net [213.105.175.153]
6 13 ms 9 ms 70 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
7 14 ms 13 ms 24 ms tge8-1.fr3.lon.llnw.net [87.248.208.129]
8 30 ms 17 ms 17 ms tge7-2.fr3.ams.llnw.net [69.28.171.93]
9 20 ms 31 ms 18 ms ve5.fr4.ams.llnw.net [69.28.172.114]
10 36 ms 19 ms 19 ms giganews.ve212.fr4.ams.llnw.net [87.248.196.14]
11 * 17 ms * 216-196-108-133.ams.giganews.com [216.196.108.13
3]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 35 ms * 18 ms news-europe.giganews.com [216.196.109.144]

Stabhappy · 18-09-2008, 22:00

Tracing route to news-europe.giganews.com [216.196.109.144]
over a maximum of 30 hops:

Code:

  1     2 ms     1 ms     1 ms  192.168.1.1
  2    11 ms     7 ms     7 ms  10.130.244.1
  3    11 ms     7 ms     8 ms  cdif-t2cam1-a-v110.network.virginmedia.net [62.2
54.254.41]
  4     7 ms     9 ms    11 ms  cdif-t3core-1a-ae2-0.network.virginmedia.net [19
5.182.175.197]
  5    11 ms    11 ms    14 ms  bir-bb-a-so-120-0.network.virginmedia.net [212.4
3.162.253]
  6    18 ms    12 ms    12 ms  nth-bb-b-so-220-0.network.virginmedia.net [62.25
3.185.85]
  7    14 ms    17 ms    14 ms  tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
  8    26 ms    26 ms    22 ms  tge8-1.fr3.lon.llnw.net [87.248.208.129]
  9    31 ms    45 ms    26 ms  tge7-2.fr3.ams.llnw.net [69.28.171.93]
 10    26 ms    32 ms    21 ms  ve5.fr4.ams.llnw.net [69.28.172.114]
 11    27 ms    21 ms    21 ms  giganews.ve210.fr4.ams.llnw.net [87.248.196.6]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *       22 ms     *     news-europe.giganews.com [216.196.109.144]
 21    23 ms    22 ms    23 ms  news-europe.giganews.com [216.196.109.144]

Trace complete.

Regardless, I'm hitting the cap speed (2400kb/s) on 10 connections.

18-09-2008, 23:26

Code:

09/18/08 23:25:18 Fast traceroute news-europe.giganews.com
Trace news-europe.giganews.com (216.196.109.144) ...
 1 192.168.1.1       2ms    1ms    2ms  TTL: 64  (No rDNS)
 2 10.249.136.1      8ms   18ms   12ms  TTL:255  (No rDNS)
 3 82.13.48.193     17ms   12ms   11ms  TTL:254  (nott-t2cam2-b-v613.network.virginmedia.net ok)
 4 195.182.175.145  12ms   13ms   14ms  TTL:252  (nott-t3core-1b-ae4-0.network.virginmedia.net ok)
 5 213.105.174.173  18ms   15ms   20ms  TTL:251  (nth-bb-b-as1-0.network.virginmedia.net ok)
 6 62.253.184.2     15ms   43ms   36ms  TTL:250  (tele-ic-1-as0-0.network.virginmedia.net ok)
 7 87.248.208.129   18ms   21ms   28ms  TTL: 57  (tge8-1.fr3.lon.llnw.net ok)
 8 69.28.171.93     24ms   24ms   26ms  TTL: 58  (tge7-2.fr3.ams.llnw.net ok)
 9 69.28.172.114    23ms   23ms   29ms  TTL: 57  (ve5.fr4.ams.llnw.net ok)
10 87.248.196.14    24ms   27ms   27ms  TTL:249  (giganews.ve212.fr4.ams.llnw.net ok)
11 216.196.108.133   *     28ms   25ms  TTL:248  (216-196-108-133.ams.giganews.com probable bogus rDNS: No DNS)
12   No Response      *      *      *                 
13   No Response      *      *      *                 
14   No Response      *      *      *                 
15   No Response      *      *      *                 
16   No Response      *      *      *                 
17   No Response      *      *      *                 
18   No Response      *      *      *                 
19 216.196.109.144   *     27ms   25ms  TTL:  1  (news-europe.giganews.com ok)
20 216.196.109.144  23ms                TTL:  2  (news-europe.giganews.com ok)

I get regular 2400 KB/s using GigaNews

Ignitionnet · 19-09-2008, 10:16

I am on the ex-Telewest network, I was wondering if one of you guys on ex-ntl could post the reverse traceroute from Giganews' European server?

For the bored technical people it looks as though Virgin Media are frigging with routing or have yet more routing problems, Giganews sits on AS 30094 and peers directly with ntl's AS 5089 at Amsix - hence the return patch being that way, however in London VM are preferring to transit AS 22822 - LLNW.net - for outbound traffic.

laxity · 19-09-2008, 12:29

Quote:

Originally Posted by Broadbandings

I am on the ex-Telewest network, I was wondering if one of you guys on ex-ntl could post the reverse traceroute from Giganews' European server?

I'm ex-ntl, here you go...

news-europe.giganews.com

1 216-196-110-3.ams.giganews.com (216.196.110.3) 45 ms 0 ms 2 ms
2 216-196-108-134.ams.giganews.com (216.196.108.134) 0 ms 0 ms 0 ms
3 amst-ic-1.inet.ntl.com (195.69.144.40) 0 ms 0 ms 0 ms
4 pop-bb-a-as0-0.network.virginmedia.net (213.105.175.5) 9 ms 9 ms 19 ms
5 pop-bb-b-ae0-0.network.virginmedia.net (213.105.174.230) 9 ms 10 ms 9 ms
6 gfd-bb-a-so-010-0.network.virginmedia.net (213.105.172.137) 13 ms 11 ms 44 ms
7 glfd-t3core-1a-ge-000-0.network.virginmedia.net (213.105.175.86) 11 ms 11 ms 15 ms
8 glfd-t2cam1-a-ge-wan42.network.virginmedia.net (195.182.181.234) 11 ms 11 ms 11 ms
9 glfd-farn-ubr-3-ge01.network.virginmedia.net (80.4.30.106) 12 ms 22 ms 11 ms
10 * * *
11 * * *
12 * * *
Max number of unresponsive hops reached (firewall or filter?)

Ignitionnet · 19-09-2008, 12:48

Cheers, same path.