Unlimited & iPlayer

[#1]

to right jelv. i would like to see all the trailst to be allowed exculsive acess to thn-ag2 when adsl2 gets relesed am dreading go back in with the crowd again spotify has run perfect for around a month now on 21cn. cant say the same for the rest of the gateways

[#2]

Many are getting poor performance on 21CN - even though they are insulated from the gateway problems of non-21CN users.
If it's ever allowed to go live, it will go even slower.

Things like ping are OK - but downloads will suffer.

[#3]

How much capacity has PN bought at each of the 21CN nodes?

[#4]

They currently have a 1GBps link from one node, IIRC.  That's more than one complete central (at 622MBps) or one 'segment' (at 155MBps)
However, I don't believe the entire 1GBps is provisioned .
I do believe there is the facility to upgrade that to a 10GBps link, and when PN 'go live' they will have multiple 1GBps links from multiple nodes.
B.

[#5]

I could be 100% wrong on this, but I think that is a bit like quoting the ADSL sync speed as 8Mb, but it has been throttled to 1Mb, so sure, they may have a 1Gb/s link, but maybe they have only paid for 100Mb or less. I also thought WBC capacity was bought on a 'per node' basis.
SW.

[#6]

I think we've got about 200Mbps on the Interconnect currently.

[#7]

Is this one of those set-ups where you contract for a certain rate with BT - but are allowed to exceed this rate "at will".
But you get charged a penal rate if you do.
If so, are PN making use of this bursting facility?

[#8]

I think we get 10% extra.
Realistically, it's just like lighting 155Mbps segments on a 622Mbps pipe, but we have greater flexcibility on how much we light at a time.

[#9]

As of a couple of weeks ago PN's 21CN operation was working on a capacity of 109Mbps, according to Dave on IRC at the time - though it obviously might have changed since then.

[#10]

Quote from: Jameseh

Realistically, it's just like lighting 155Mbps segments on a 622Mbps pipe, but we have greater flexcibility on how much we light at a time.

Isn't it more flexible than the 622Mbps pipes? On those you can have a single 155MBps segment that is heavily overloaded and causing packet drops while the other three segments are under-utilised.
As 21CN is a throttled single 1Gbps link it won't get unbalanced in the same way.

[#11]

@Crucibleofevil! all gd on PN with my low 2500kbps profile if anything its the ping thats the problem
where did you get that speed test from Crucibleofevil!

[#12]

I came across it in http://www.idnetters.co.uk/forums/index.php?topic=15238.msg356352#msg356352

[#13]

Thomas - You're right, it is 109Mbps.
I think I must have read something else elsewhere and confused myself.

[#14]

speed.io is giving absolute rubbish results for the ping:

C:\Documents and Settings\John>ping 212.159.6.9
Pinging 212.159.6.9 with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=19ms TTL=250
Reply from 212.159.6.9: bytes=32 time=13ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=15ms TTL=250
Ping statistics for 212.159.6.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 31ms, Average = 19ms

[#15]

If you ping a Plusnet DNS server, you are bound to get short times.
That speed.io isn't great, in that it always gives you the highest/quickest numbers - and you don't know where it is pinging...

For example:-
ping www.rubbish.com - yes there really is such a site http://www.rubbish.com/ - it's about rubbish

Quote

Bytes Source Seq Time Units 64 72.51.27.51 1 166 ms 64 72.51.27.51 2 166 ms 64 72.51.27.51 3 166 ms 64 72.51.27.51 4 167 ms 64 72.51.27.51 5 166 ms Time minimum: 166.00 ms Time average: 166.17 ms Time maximum: 167.00 ms Packets transmitted: 5 Packets received: 5 Successful packets: 100%