1Gig speeds a bit less than expected

[Foxa]

Hello all,

I recently upgraded my 500Mbit connection with volt to 1Gig and a Hub 5, no big problems.I am wondering however, if it's possible to "tweak" things to get the best out of it .

I started out at 100Mbit and went up the ranks from there and at each stage I noticed the actual download speed exceeded my expectations every time, for the 100Mbit I would regulargy get 130_Mbit speed test results, same at 300Mbit and 500Mbit, each time I would see a good 10+20% on top of the stated figures.

When I saw that the bps links peed on the router was at 138000000Hz on the download channel states I had high hopes for the 1Gig also but.. not really there.

Various speed tests at quite times late at night and during the day have resulted in an average of 840-890Mbit, still plenty fast and well over the minimum guaranteed, but it's not quite there.

So, any tips for squeezing that last few hundred Mbits out?

I'll include my Router stats that I know how to get, if there is any other hidden data you need let me know hot to get it and I'll post it:

Cable Modem StatusItem Status Comments

Acquired Downstream Channel(Hz)	138000000	Locked
Ranged Upstream Channel(Hz)	49600000	Ranged
Provisioning State	Online	Operational

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	138000000	-4.3	39	QAM 256	1
2	146000000	-4.3	39	QAM 256	2
3	154000000	-4.3	39	QAM 256	3
4	162000000	-4.3	39	QAM 256	4
5	170000000	-4.4	39	QAM 256	5
6	178000000	-4.3	40	QAM 256	6
7	186000000	-4.1	40	QAM 256	7
8	194000000	-3.8	40	QAM 256	8
9	202000000	-3.8	40	QAM 256	9
10	210000000	-3.5	40	QAM 256	10
11	218000000	-3.4	40	QAM 256	11
12	226000000	-3.4	40	QAM 256	12
13	234000000	-3.3	40	QAM 256	13
14	242000000	-3.4	40	QAM 256	14
15	250000000	-3.6	41	QAM 256	15
16	258000000	-3.7	41	QAM 256	16
17	266000000	-3.2	41	QAM 256	17
18	274000000	-3.1	41	QAM 256	18
19	282000000	-2.9	41	QAM 256	19
20	290000000	-2.9	41	QAM 256	20
21	298000000	-3	41	QAM 256	21
22	306000000	-3.1	41	QAM 256	22
23	314000000	-3.1	41	QAM 256	23
24	322000000	-3.2	41	QAM 256	24
25	330000000	-3.3	41	QAM 256	25
26	338000000	-3.2	40	QAM 256	26
27	346000000	-3.4	41	QAM 256	27
28	354000000	-3.7	40	QAM 256	28
29	362000000	-3.5	41	QAM 256	29
30	370000000	-3.6	40	QAM 256	30
31	378000000	-3.5	40	QAM 256	31

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	39	3353177	2216
2	Locked	39	17351067	6779
3	Locked	39	3681	1699
4	Locked	39	3588	1815
5	Locked	39	3513	1033
6	Locked	40	5290	2014
7	Locked	40	1506	1396
8	Locked	40	1304	1364
9	Locked	40	1166	1559
10	Locked	40	1745	1890
11	Locked	40	1754	1562
12	Locked	40	1952	2899
13	Locked	40	678	633
14	Locked	40	1349	1498
15	Locked	41	1140	1601
16	Locked	41	892	1338
17	Locked	41	396	539
18	Locked	41	952	1493
19	Locked	41	879	1345
20	Locked	41	2306	1642
21	Locked	41	2925	1688
22	Locked	41	2230	1041
23	Locked	41	3485	1809
24	Locked	41	2625	1560
25	Locked	41	2374	1417
26	Locked	40	807	478
27	Locked	41	1037	1175
28	Locked	40	573	542
29	Locked	41	1201	1345
30	Locked	40	469	495
31	Locked	40	689	912

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	49600000	56	5120	QAM 64	1
1	43100000	55.8	5120	QAM 64	2
2	36600000	55.3	5120	QAM 64	3
3	30100000	55.3	5120	QAM 64	4
4	23600000	54.5	5120	QAM 64	9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	1	0
4	ATDMA	0	0	0	0

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

1

Enabled

3.1

cmreg-vmdg660-bbt076-b.cm

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

158076

1230000450 bps

42600bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

158075

55000270 bps

42600bytes

0 bps

42600bytes

Best Effort

[Foxa]

Thought I'd include the Log

Network Log

Time Priority Description

28-02-2023 10:21:03	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:19:06	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:18:57	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:17:06	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:17:06	notice	CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.
28-02-2023 10:17:06	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;C
28-02-2023 10:17:06	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:17:06	notice	CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:16:39	warning	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:16:16	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:16:11	warning	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:16:06	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:16:05	warning	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-02-2023 10:16:05	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 14:58:30	notice	REGISTRATION COMPLETE - Waiting for Operational status
27-02-2023 14:58:22	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 14:58:10	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 14:58:08	notice	Honoring MDD; IP provisioning mode = IPv4
27-02-2023 14:58:01	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 14:57:56	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 14:57:43	critical	Cable Modem reboot from UI
27-02-2023 14:43:28	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 14:43:17	critical	Cable Modem Reboot due to power button reset
27-02-2023 13:20:42	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:20:27	critical	DHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:20:26	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:13:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:11:17	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:11:17	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:11:13	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-02-2023 13:11:00	critical	Cable Modem Reboot due to SW Upgrade
27-02-2023 13:04:34	critical	Cable Modem Reboot from SNMP

[Client62 · Accepted solution]

A single 1000Mb/s or 1Gb/s network connection has a transfer limit of about 940Mb/s.

To reach the full 1140Mb/s speed on a single device the connection is going to have to be made at 2.5Gb/s.

This perhaps means adding a 2.5Gb/s network adaptor to the computer.

As the computer is already topping out at 840-890Mb/s there may not be any more speed to be had.

If your VM Hub is in Router mode this link will show the service speed at the Hub : https://www.samknows.com/realspeed/

[Foxa]

Interesting, thank you very much for the info, soo.... the hub seem to be right on the money speed wise, it's my dinosaw networking kit that needs a revamp..... OK, That I can do, thanks!

[Foxa]

Just as a side note, I unplugged the network cable and used wifi... got 1109Mbit heh.

[carl_pearce]

I'd suggest your upstream power levels are a touch high, which could be causing an inconsistent connection.

You wouldn't really expect to see any, maybe the odd one, 'Post RS Errors' either.

[Foxa]

Ok, are the post RS error typically a sign of something? I know I had an engineer out a while back who said my signal levels were a little low, basically flat after flat in my building have been spurred off the same cable with passive splitters.

I take it my slightly low -4dbm inbound is in keeping with the slightly high outbound, i.e. lower than idea signal.

Any suggestions?.

[Foxa]

I did a reboot at 6pm and this was the download report at 8:40pm

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	39	15	0
2	Locked	39	14	1
3	Locked	39	0	0
4	Locked	40	1	0
5	Locked	40	1	0
6	Locked	40	1	0
7	Locked	40	2	0
8	Locked	40	8	10
9	Locked	40	1	0
10	Locked	40	7	0
11	Locked	40	5	13
12	Locked	40	7	9
13	Locked	41	19	0
14	Locked	41	12	0
15	Locked	41	0	0
16	Locked	41	0	0
17	Locked	41	1	0
18	Locked	41	9	0
19	Locked	41	0	0
20	Locked	41	0	0
21	Locked	41	0	0
22	Locked	41	0	0
23	Locked	41	1	0
24	Locked	41	1	0
25	Locked	41	0	0
26	Locked	41	0	0
27	Locked	41	0	0
28	Locked	41	0	0
29	Locked	41	0	0
30	Locked	41	0	0
31	Locked	41	1	0

[carl_pearce]

VM will respond to this thread in a few days, and will advise if an engineer visit is required.

For now you are getting a least decent speeds.

[Foxa]

OK, thanks.