I found a better speed test for satellite internet

[Bandwidth]

Enough with the bickering like little kids. Are you guys really arguing over a speed test?

Stay on topic or do not post. Thank you.

Thank you VERY much!

[rockymtnhigh]

Thank you VERY much!

Uh... I was talking to you too.

[TNGTony]

beat me to it.

[tobifelinis]

Very true. Bwporker proves this by his original post. I take some responsibility because the tests were poorly described and usage instructions were lacking a bit, actually a lot. We've seen the problem before. I still stand behind the results of both the TCP and Speed/Cap Tests and they should be a reasonable benchmark for those who know how to use the tests. The Route Quality may be pretty useless for you guys however as it's served from the server outward. BUT BUT BUT there is another way around this problem. I'm going to pm you a link where you can download run an applet that will essentially run the route test in reverse. You game? If so I'll prepare it tonight and have it to you by tomorrow mid day. I'm spent and need to get some work done.

Im game I got time to play.

I don't really understand the purpose of the Speed/Cap test

What good to me is it to know the max capacity of the satellite link or what ever gets measured if my subscription plan has no where close to that capacity. Here is one I ran today , But it really does not tell me anything useful to me that I can tell.

Capacity test statistics
------------------------
Download capacity: 5032200 bps
Download packets per second: 629
Upload capacity: 22408 bps
Upload packets per second: 2
Quality of service: 55 %
Packet size: 1000 Bytes

I have run the tsp speed test a few times it seems to be consistant with the Hughes speed test. I kinda like the speed display that shows the comparison with other services.

peed test statistics
---------------------
Single TCP Session Download speed: 960784 bps
Single TCP Session Upload speed: 127344 bps
Download quality of service: 89 %
Upload quality of service: 8 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 549 ms
Average download pause: 13 ms
Minimum round trip time to server: 2688 ms
Average round trip time to server: 3091 ms
Your estimated available download bandwidth: 17600000bps
Route concurrency: 18.318373
Download TCP forced idle: 99 %
Maximum route speed: --


All my test are on your logs under beau.

[Bandwidth]

Im game I got time to play.

I don't really understand the purpose of the Speed/Cap test

What good to me is it to know the max capacity of the satellite link or what ever gets measured if my subscription plan has no where close to that capacity. Here is one I ran today , But it really does not tell me anything useful to me that I can tell.

Capacity test statistics
------------------------
Download capacity: 5032200 bps
Download packets per second: 629
Upload capacity: 22408 bps
Upload packets per second: 2
Quality of service: 55 %
Packet size: 1000 Bytes

I have run the tsp speed test a few times it seems to be consistant with the Hughes speed test. I kinda like the speed display that shows the comparison with other services.

peed test statistics
---------------------
Single TCP Session Download speed: 960784 bps
Single TCP Session Upload speed: 127344 bps
Download quality of service: 89 %
Upload quality of service: 8 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 549 ms
Average download pause: 13 ms
Minimum round trip time to server: 2688 ms
Average round trip time to server: 3091 ms
Your estimated available download bandwidth: 17600000bps
Route concurrency: 18.318373
Download TCP forced idle: 99 %
Maximum route speed: --


All my test are on your logs under beau.

I'll do my best to explain the differences.

The speed/cap test is designed to measure the data capacity limit of a connection and reports the maximum data throughput for download and upload transfers while eliminating any throughput reductions invoked as a result of TCP overhead.

During the test it sends multiple streams of data simultaneously until it fills the available bandwidth for a given connection. It does this primarily because it does not care about the distance travelled, the packet order or even the packets that get lost because of the increased contention.

The test simply reports the capacity speed of the connection based on the volume of data that survives the journey and arrives at the destination. The speed/cap application can take this approach primarily because it does not care about the distance travelled, the packet order or even the packets that get lost because of the increased contention. As the speed/cap application does not care about the order of the data or the trip time for a connection, it can deliver an incorrect and/or misleading result.

The TCP Speed Test

Tests and measures the data speed and flow between remote you and our server, unlike the Speed/Cap Test this test sends only one stream of data, takes into account packet order, loss, etc in formulating the results.

Both tests should be used together when formulating an overall rating for your connection.

As an example my TCP Speed from my home system gives me about 8.6 mbps per second on a consistent basis with a "available bandwidth of about 33 to 36mpbs) and the Speed/Cap shows a consistent 35mpbs which is exactly where I should be. Funny thing is when I run my laptop via wireless at home my TCP speed increases to almost 14mbps and my Speed/Cap drops to about 33mbps consistently.

What it boils down to is that the main pc routes differently within my home network (and I also have some issues with the hardline nic and cabling that I'm already aware of).

Just for reference a normal TCP Speed test rating for MY home network should be between 10-15 mbps (with an approximate available bandwidth of about 33mpbs to 37mbps) depending on network conditions at the moment provided I have no loss or other issues and I see exactly those results with the wireless connection and other pc's within the house.

Each test has it's merits and when combined together you will get a very good view into the health of your network and external broadband connection. The trick is learning how to interpret the results. On each of our tests we've included a description and how to interpret the data, unfortunately most people never read it.

I hope this explains it a little better.

[tobifelinis]

I am sorry Bandwith but I am just a dumb helicopter pilot. I did not understand any of that.

I ran the route test a couple of more times and on one test it looked like it actually made it past the NAT router and across to my modem. At least it showed it and the time was 1600ms which would be pretty close to correct. Unfortunately I did not screen copy it. I can not get it to do it again and it currently stops at the NOC.

But something from your severer is making it to my firewall not sure what all this is.

If I did not have some idea of where it was coming from I would be loking things down tighter.

[Bandwidth]

I am sorry Bandwith but I am just a dumb helicopter pilot. I did not understand any of that.

I ran the route test a couple of more times and on one test it looked like it actually made it past the NAT router and across to my modem. At least it showed it and the time was 1600ms which would be pretty close to correct. Unfortunately I did not screen copy it. I can not get it to do it again and it currently stops at the NOC.

But something from your severer is making it to my firewall not sure what all this is.

If I did not have some idea of where it was coming from I would be loking things down tighter.

The above wasn't referring to the Route Test. I may have a fix for your Route issue in just a bit. In the meantime I would like you to run the following

(removed the remote agent access as it serves no purpose at this time)

Give it a try and lets see if that maps everything from your location outward. No promises but it never hurts to try. Just enter your SID, click download, then run and run. THIS INSTALLS NO SOFTWARE - JUST A RUNTIME REMOTE AGENT and it terminates the minute the test is done.

[tobifelinis]

I ran it two times with turbo page on and two times with turbo page off.

I don't see it in my log file.

[Bandwidth]

I was afraid of that Tobi. Several people did run the remote agent and the results were unfortunately unsatisfactory, actually the agent was useless. I experienced similar results with a similar test on a different network as well. It was a great idea, just didn't turn out the way I'd hoped.

I'll complete the other tests by weeks end and I'm pretty sure we'll keep the route test for network issues outside your providers network, it's still valuable there especially when we open up the route to be traced. Right now it's to our server only, soon options will be available to trace to any destination.

The other tests should perform decently for their intended purpose and they will also remain.

[bwporker]

So you will still have the tests available?