In reply to a post by Ignitionnet:

As an aside having a second line installed and enabled for FTTC imminently. Anyone done thing, and how much of a performance hit did you note on the original line?

Answering my own question in my case there was indeed a hit, attainable has dropped by about 3Mb down, and 1Mb up due to loss of 0.8dB SNRM in each direction.

Max: Upstream rate = 23850 Kbps, Downstream rate = 77384 Kbps
Path: 0, Upstream rate = 19999 Kbps, Downstream rate = 79891 Kbps

Down Up
SNR (dB): 5.3 14.3

quite a small hit compared to what I have seen others report.

Throughput.

1/7/2014 8:52 AM GMT 115.98 Mb/s 26.38 Mb/s 33 ms London ~ 150 mi

I'm jealous... What router is doing the load balancing?

I was first on my CAB. And very close <50M from Fibre aggregation node (CAB is 20M away from FTTC cabinet). I was getting a perfect line about 105Mb down and 35Mb up with 0 errors... as more people joined I wouldn't notice much... a few more errors and maybe a couple of Mb of attainable lost...

My next door neighbor joined and it went down from 78Mb to 70Mb attainable... I imagine this is a classic example of cross-talk.

Tim

how fast is the 2nd line syncing?

In reply to a post by Chrysalis:

how fast is the 2nd line syncing?

I'm not sure. The Royal Fail have my 2nd Huawei sitting somewhere in the ether in between seller and myself.

EDIT: 73.9-ish, IP Profile is 71.55.

Edited by deleted (Tue 07-Jan-14 18:54:22)

A hit on Attainable is not really a hit though, is it?

It is a deferred hit that will land when that line resynchs.

In what way?

In reply to a post by BatBoy:

In what way?

The attainable has dropped, the line is currently synched higher than the attainable and when next resynched will sync lower due to the performance hit on the line.

The performance hit will manifest at the next resync event.

EDIT: In actual fact it shows at a very low level now with increased error rates. A touch of packet loss from time to time though nothing major.

Edited by deleted (Wed 08-Jan-14 11:09:18)