If the check files from us are good speed it suggests

a) A PC issue with java
b) Traffic management issues, i.e. the files use different ports and can be identified as HTTP traffic by traffic management hardware even when not on port 80
c) The issue is not a routing one
d) You cannot conclude its a problem with the speed test server, since all users from all ISP's use the servers and would be equally affected.
e) The bbc tester is just another speed tester and does not seem to do anything specifically to test streaming capabilities

Problem Solved!!!

I reinstalled Java, and now the speed tester will run on Port 80.

on Port 8095 - 282/378 kbps
on Port 80 - 5861/378 kbps

Now I have to apologise to Virgin.

Many thanks MrSaffron

In reply to a post by ipple2meet:

Problem Solved!!!

I reinstalled Java, and now the speed tester will run on Port 80.

on Port 8095 - 282/378 kbps
on Port 80 - 5861/378 kbps

Now I have to apologise to Virgin.

Many thanks MrSaffron

Errr - you have to apologise to them for throttling you, which is what they are doing except on port 80?

Edited by RobertoS (Fri 03-Jul-09 13:06:21)

Re - Errr - you have to apologise to them for throttling you, which is what they are doing except on port 80?
-------------------------------------------
Could you please explain this.

OK I am happy to show my ignorance in that I do not understand what the Port 80 c/f 8095 thing means.

All I can see is that the thinkbroadband speed test on Port 80 is giving the same results as the bbc tester and the thinkbroadband file tests. However, with thinkbroadband on Port 8095 I get the lower figures, which sometimes (not always) seem to be reflected in the real world when I am streaming.

I have not yet apologised to virgin.

Hi
I have not yet apologised to virgin.

I wouldn't apologise . The problem is that VIRGIN are throttling port 8095 . If they didnt you would not have had the problem !!! that might be the reason you have problems when streaming.

Regards Jeff

Edited by deleted (Fri 03-Jul-09 23:10:08)

As per jeffbb, and my earlier post.

Port 80 is the one used by browsers and is rarely throttled by any ISP as it would (a) not actually help a lot in reducing the load on their servers, and (b) be quickly noticed by anyone with technical knowledge. So they could get a bad reputation for little benefit.

Throttling ports used for streaming and P2P (DVD/film/music downloads) is what helps the ISP to get away with minimal capacity provision for the maximum number of customers. Heavy downloaders recognise the symptoms and migrate. Normal users just think the internet or their connection is slow at the time, and assume (incorrectly) that it is just the way things are on the internet.

So if you do the TBB speed test on 8095 it correctly reports what you are getting supplied from your ISP, and experience when streaming.

If you do it on Port 80 it tells you what your ISP is allowing on your browser.

Speedtesters such as speedtest.net, BBMax and IO use Port 80.

Port 80 results are as near as you will get to knowing your true line capability between you and the exchange. TBB on port 8095 is telling you the truth about actual performance of your ISP.

Think of the number of turnstiles at a sports ground. A small number cuts staff and equipment costs dramatically - but many punters miss the start of the match. A good stadium has enough turnstiles to get everyone in on time. Tickets probably cost more. Club members have a special entrance with a nice wide gate.

I'm not sure how clear all that is as I've had a very pleasant few glasses of wine and an excellent brandy, but I hope it helps.

In reply to a post by ipple2meet:

Now I have to apologise to Virgin.

Actually if you're on Virgin ADSL, you need to close your account, get your MAC code, and find a much better ISP.

Your line can do 5.8mbps for web pages, yet for the speedtest it did 282kbps. That's a stunning difference.

If you use your connection only for email and web then you might not notice, but if you use it for anything such as video streaming, or home working (VPN) then you would almost certainly be better off on a more honest ISP. Look to O2, NewNet, ID.NET or Sky as those who don't mess with your connection.

In reply to a post by RobertoS:

I'm not sure how clear all that is as I've had a very pleasant few glasses of wine and an excellent brandy, but I hope it helps.

Hope I've assisted; but the few cans may leave me in the same state

Edited by jchamier (Sat 04-Jul-09 01:12:43)

I am grateful for the further contributions to this subject.

The current issue to me is that, whereas I was convinced a year ago that the virgin service was poor, I cannot now be sure. In the last hour, using tbbMeter as a monitor, I have seen the following:

1) I have watched Sky News. The initial buffering measured 4Mbps on the meter, then settled to around 2Mbps. Performance was fine.

2) I have my own website which streams audiovisual presentations. This is one of the sites which sometimes in the past allerted me to low virgin performance.
In the last hour tbb showed over 2.5Mbps initial buffering, and performance was fine.

3) A utube video gave 4.5Mbps initial buffering on tbbMeter.

4) On the thinkbroadband tests, immediately after, Port 80 gave 5.6Mbps, and Port8095 gave 120kbps. These speeds were confirmed on the tbbMeter whilst doing the tests.

So I have satisfactory internet at a a time when the normal thinkbroadband test says it is 120kbps.

Now I am going to have a few glasses of wine. Thanks again.

In reply to a post by ipple2meet:

So I have satisfactory internet at a a time when the normal thinkbroadband test says it is 120kbps.

TBB said it was slow (120 Kbps) ONLY on non-Web activities (Port 8096). It reported faster (5.6 Meg) on Web browsing (port 80).

All your examples were Web activities; so TBB agreed with them.

The 120Kbps is a result of what Virgin Media are doing, i.e. if you run another app on those ports it would be slow too.

It is called traffic management