2.32e slower than 2.32d or stats different?

[peterb99]

On my 7800DXL I saved my 2.32d settings to file, updated to 2.32e and then loaded the settings back. From previous threads this seems to be an acceptable method of quickly getting all original settings back after a firmware update.

However on 2.32e I was seeing some wierd stats - SNR downstream consistent at around 14 and, as a result, lower Attainable and Rate speeds - around 3400 and 3200. I should have captured the stats to post but decided to downgrade back to 2.32d and these are the stats I see, immediately after the router has started and connected to my isp:

billionstats.png

I ran a http://www.broadbandspeedchecker.co.uk/ test before and after the downgrade and got similar results though with 2.32d the SNR previously came down to around 6.3 with, I assume, corresponding speed increases and hopefully this will happen again now I've reverted to 2.32d.

I think I will stay with 2.32d as it works fine and may give me a placebo or real speed increase. Just wondering if anyone else has had the same experiences or any thoughts on this? My isp is Plusnet, fwiw.

Thanks!

Pete

[billion_fan]

On my 7800DXL I saved my 2.32d settings to file, updated to 2.32e and then loaded the settings back. From previous threads this seems to be an acceptable method of quickly getting all original settings back after a firmware update.

However on 2.32e I was seeing some wierd stats - SNR downstream consistent at around 14 and, as a result, lower Attainable and Rate speeds - around 3400 and 3200. I should have captured the stats to post but decided to downgrade back to 2.32d and these are the stats I see, immediately after the router has started and connected to my isp:

billionstats.png

I ran a http://www.broadbandspeedchecker.co.uk/ test before and after the downgrade and got similar results though with 2.32d the SNR previously came down to around 6.3 with, I assume, corresponding speed increases and hopefully this will happen again now I've reverted to 2.32d.

I think I will stay with 2.32d as it works fine and may give me a placebo or real speed increase. Just wondering if anyone else has had the same experiences or any thoughts on this? My isp is Plusnet, fwiw.

Thanks!

Pete

No issues here (see attached screen shots) SNR is the same

[peterb99]

OP here again. In view of the previous response I've tried again and this is what I get now:

try2.png

I think my line must be funny as, for example, I don't understand why the 2.32d Attainable Rate is lower than the Rate. Possibly my misunderstanding.

The downstream Rate under 2.32e is 1000 lower than 2.32d. The screenshots were taken before and then shortly after the update from 2.32d to 2.32e. The router uptime for each was an hour or less. Maybe 2.32e will increase given time?

Possibly I'm being too anal about this and I should just be pleased I have a stable, if not terribly fast, internet connection?

I'm interested in understanding the comparison between the 2 sets of stats more though. So I stop making stoopid posts.

Thanks.

Pete

[billion_fan]

OP here again. In view of the previous response I've tried again and this is what I get now:

try2.png

I think my line must be funny as, for example, I don't understand why the 2.32d Attainable Rate is lower than the Rate. Possibly my misunderstanding.

The downstream Rate under 2.32e is 1000 lower than 2.32d. The screenshots were taken before and then shortly after the update from 2.32d to 2.32e. The router uptime for each was an hour or less. Maybe 2.32e will increase given time?

Possibly I'm being too anal about this and I should just be pleased I have a stable, if not terribly fast, internet connection?

I'm interested in understanding the comparison between the 2 sets of stats more though. So I stop making stoopid posts.

Thanks.

Pete

It could be your line mate, as this attainable rate being lower then the sync rate was reported on 2.32e, but you have the same issue on the 2.32d, so I think BT are playing around at the moment, and haven't really resolved what ever was changed

Staying on 2.32e might increase your sync rate over time (once the line has been up for a couple of weeks) but you have the SNR tweak to fall back on (it looks like the SNR is reason for lower sync rate on the 2.32e)

[peterb99]

It could be your line mate, as this attainable rate being lower then the sync rate was reported on 2.32e, but you have the same issue on the 2.32d, so I think BT are playing around at the moment, and haven't really resolved what ever was changed

Staying on 2.32e might increase your sync rate over time (once the line has been up for a couple of weeks) but have the SNR tweak to fall back on (it looks like the SNR is reason for lower sync rate on the 2.32e)

Thanks. But in my screenshot it's only 2.32d where Rate > Attainable. However, I'm sure you're right about letting it settle down a bit. I was getting faster speeds a couple of weeks back. The only thing that changed (I thought) was me messing about with the firmware updates but maybe there's more going on elsewhere that's affecting it.

Thanks for taking the trouble to respond!

Pete

[billion_fan]

It could be your line mate, as this attainable rate being lower then the sync rate was reported on 2.32e, but you have the same issue on the 2.32d, so I think BT are playing around at the moment, and haven't really resolved what ever was changed

Staying on 2.32e might increase your sync rate over time (once the line has been up for a couple of weeks) but have the SNR tweak to fall back on (it looks like the SNR is reason for lower sync rate on the 2.32e)

Thanks. But in my screenshot it's only 2.32d where Rate > Attainable. However, I'm sure you're right about letting it settle down a bit. I was getting faster speeds a couple of weeks back. The only thing that changed (I thought) was me messing about with the firmware updates but maybe there's more going on elsewhere that's affecting it.

Thanks for taking the trouble to respond!

Pete

Yes I know on your 2.32d, the attainable rate is lower then your sync rate (which should be the other way around, like 2.32e), what I meant was I had this report on firmware 2.32e, but for your tests it seems the other way round (2.32d has the same issue), so there must be other external factors that's causing this (as this issue wasn't there when 2.32d was released, so something must of changed)

[peterb99]

Yes I know on your 2.32d, the attainable rate is lower then your sync rate (which should be the other way around, like 2.32e), what I meant was I had this report on firmware 2.32e, but for your tests it seems the other way round (2.32d has the same issue), so there must be other external factors that's causing this (as this issue wasn't there when 2.32d was released, so something must of changed)

Thanks for the clarification.

Cheers,

Pete