Oh my word...

PuncH · Jun 13, 2009, 20:24:21

Finally been able to get onto the BT speedtest.

Looks like a stuck profile $:-\$

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 21803 kbps(DOWN-STREAM), 1231 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 6569 kbps

PuncH · Jun 13, 2009, 22:37:32

Just rebooted my router as I hadn't done that since the regrade...

Perhaps my profile will gradually go up over the next few days? I'll not trouble IDNet just yet

PuncH · Jun 14, 2009, 00:08:48

Got back onto the BT speedchecker after the 3 hour wait. Looks like the router reboot did the trick.

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 20911 kbps(DOWN-STREAM), 1227 kbps(UP-STREAM)
IP profile for your line is - 18000 kbps
Actual IP throughput achieved during the test was - 11772 kbps

Looks like that's pretty much the maximum I'll get. Not sure why the throughput is 7mb less than my profile but all the BT/IDNet tests suggested I'd get around 11mb.

Sebby · Jun 14, 2009, 00:21:22

You'll always lose a bit in overheads, but that does look a bit low. It might be worth having a look at your MTU and RWIN.

PuncH · Jun 14, 2009, 00:29:30

Quote from: Sebby on Jun 14, 2009, 00:21:22
You'll always lose a bit in overheads, but that does look a bit low. It might be worth having a look at your MTU and RWIN.

I may well do Sebby. MTU is set at 1458 on the router. No idea about the RWIN.

I think I'll just leave it well alone for a few days and let it all settle down before I start messing around with it. If it stays like this I would have doubled my throughput, and trebled my upload speed which is pretty darn good really.

PuncH · Jun 14, 2009, 09:17:56

Looks like it's getting there, unless of course the result's a little false because everyone's still in bed

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 20911 kbps(DOWN-STREAM), 1227 kbps(UP-STREAM)
IP profile for your line is - 18000 kbps
Actual IP throughput achieved during the test was - 15751 kbps

ThinkBroadband speedtest:

Speed Down 16721.87 Kbps ( 16.3 Mbps )
Speed Up 1035.99 Kbps ( 1 Mbps )

Line is very stable with just one or two re-syncs early yesterday when I first started using the new service.

Think I'll post is the succesfull conections thread in a day or two.

Rik · Jun 14, 2009, 10:01:07

Looking good, Jonathan.

Rik · Jun 14, 2009, 10:01:30

Quote from: PuncH on Jun 14, 2009, 00:29:30
I may well do Sebby. MTU is set at 1458 on the router. No idea about the RWIN.

I think I'll just leave it well alone for a few days and let it all settle down before I start messing around with it. If it stays like this I would have doubled my throughput, and trebled my upload speed which is pretty darn good really.

Open it to 1500.

PuncH · Jun 14, 2009, 10:21:54

So I need to take into consideration the overheads in the MTU setting, or do I just change it to 1500?

I've done a test and 1472 is the max MTU size that doesn't need fragmenting on the ping test, so adding the overheads to that gives me 1500

What about the network adaptor on my laptop?

Rik · Jun 14, 2009, 10:23:39

Set the router to 1500, make any adjustments inside Windows. I'd start at 1500 and work down if you need to.

PuncH · Jun 14, 2009, 10:29:58

I've set the router to 1500. It's on the WAN setup page on my netgear.

If it's not right what sort of behaviour would I notice?

With the MTU set to 1458 beforehand, was it too small I take it, or did it just mean I wasn't making the most of my router?

Rik · Jun 14, 2009, 10:34:54

The MTU controls the packet size, so the smaller it is, the more packets are required for a given quantity of data. As each packet has overheads and has to be processed, this slows things down. However... if the packet size (MTU) is more than can be handled by your connection at any point, the packets get defragmented and transmission becomes slower. On IDNet, I generally find 1500 works best, some people have had better results at 1458. On AOL, you'd need to use 1430.

Sebby · Jun 14, 2009, 11:11:41

You don't need to adjust the MTU for overheads, just take it into consideration. For example, if you can use an MTU of 1472 without packets being fragmented, you should set an MTU of 1500 (1472 + 28 for overheads).

PuncH · Jun 14, 2009, 11:46:55

Quote from: Sebby on Jun 14, 2009, 11:11:41
You don't need to adjust the MTU for overheads, just take it into consideration. For example, if you can use an MTU of 1472 without packets being fragmented, you should set an MTU of 1500 (1472 + 28 for overheads).

Nice...thanks guys.

I did a ping test with a packet size of 1473 and it had to be fragmented, whereas 1472 was fine. So I've set the MTU on the router to 1500. So it seems the best thing is to set the MTU as big as you can to make the most of the network?

I've also checked the Microsoft site for xbox live and that needs a minimum MTU of 1368 so that's cool.

Have a karma the pair of you!

Lance · Jun 14, 2009, 11:57:15

Quote from: PuncH on Jun 14, 2009, 11:46:55
So it seems the best thing is to set the MTU as big as you can to make the most of the network?

Spot on!

Rik · Jun 14, 2009, 11:57:23

If it works at 1500 then that's the best size, Jonathan, and it does for most people.

PuncH · Jun 14, 2009, 12:24:31

Quote from: Rik on Jun 14, 2009, 11:57:23
If it works at 1500 then that's the best size, Jonathan, and it does for most people.

It seems to work fine

Although it looks like there's been a re-sync sometime this morning. I've been busy on and off so the laptop's been sleeping!

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 19690 kbps(DOWN-STREAM), 1225 kbps(UP-STREAM)
IP profile for your line is - 17000 kbps
Actual IP throughput achieved during the test was - 15171 kbps

Doesn't seem to have affected the throughput though. In fact I have a feeling the line is going to settle at around this mark.

Line stats:

ADSL Link Downstream Upstream
Connection Speed 19690 kbps 1225 kbps
Line Attenuation 16.0 db 6.8 db
Noise Margin 8.5 db 6.3 db

Rik · Jun 14, 2009, 12:26:14

You've got some headroom on the noise margin, so I wonder if the target has been set to 9db? It might be worth running Routerstats so you can see what the margin is immediately after a re-sync.

PuncH · Jun 14, 2009, 12:35:07

I've got it running at the moment. NM is 8.5 currently.

I don't mind if it's been set to 9db. It's not affecting the speed adversly and gives me a little room for manouvre.

Rik · Jun 14, 2009, 12:37:46

It could explain the re-sync this morning, turning interleaving on (step one) or raising the target NM (step 2) will both trigger a re-sync and are done in response to the error count on the line.

PuncH · Jun 14, 2009, 12:52:50

According to routerstats the interleave depth on the downstream side is now 96!?

But at the bottom of the telnet page it says interleave is off.

Rik · Jun 14, 2009, 12:53:37

I didn't know Routerstats could find interleave depth, tbh.

PuncH · Jun 14, 2009, 13:04:58

From the downstream;

Noise Margin: 8.6 dB
Connection Rate: 19690 Kbps
Line Attenuation: 16.0 dB
Power: 0.0 dBm
Max Rate: 24452 Kbps

SF: 790983
SF Errors: 237
Reed Solomon: 202491852
RS Corrected: 30033
RS Un-Corrected: 19291
HEC: 221
Errored Seconds: 432
Severe ES: 7
Interleave Depth: 96

Rik · Jun 14, 2009, 13:08:42

Intriguing. As far as I know, there are only 5 levels of interleave and WBC.

Perhaps it's a measure of the time delay or something similar?

Sebby · Jun 14, 2009, 13:20:34

Quote from: PuncH on Jun 14, 2009, 11:46:55
Nice...thanks guys.

I did a ping test with a packet size of 1473 and it had to be fragmented, whereas 1472 was fine. So I've set the MTU on the router to 1500. So it seems the best thing is to set the MTU as big as you can to make the most of the network?

I've also checked the Microsoft site for xbox live and that needs a minimum MTU of 1368 so that's cool.

Have a karma the pair of you!

Exactly right. Thanks for the karma.