1.3mbps tethering, 551kbps mobilespeedtest?

[chronster]

How is it I can tether my laptop and get 1.3mbps download speed from speedtest, then from my phone (in IE) I only get 551kbps at mobilespeedtest?

Is there a registry setting or something I should look at?

I'm on Sprint btw.

[JTuck]

From what I read you will always get faster speeds tethering due to the slow processor and whatnot on the phone.

[chronster]

Originally Posted by JTuck

From what I read you will always get faster speeds tethering due to the slow processor and whatnot on the phone.

Well see, I've read people reporting 1.3mpbs from their phone, so i know the processor is capable of those speeds. Perhaps when the phone is getting that speed, tethering is even faster?

I'm confused lol

[chronster]

I just set my TCP Receive Window to like 65500 or something from 98800 or something. A smaller value resulted in higher results at mobilespeedtest, how is this possible?

Anyways, I went from 550 kbps to 1.2mbps on the 1mb download test. This is odd...

I can get 1. something Mbps on mobilespeedtest. You need to have good signal and most importantly use the 1MB download file. When you first go to the site it uses a smaller file that will never max out the connection and you will only get like 500-700 Kbps. Then after it finishes at the bottom it says re-test and use the 1MB or 2MB file.

[chronster]

Originally Posted by b194331

I can get 1. something Mbps on mobilespeedtest. You need to have good signal and most importantly use the 1MB download file. When you first go to the site it uses a smaller file that will never max out the connection and you will only get like 500-700 Kbps. Then after it finishes at the bottom it says re-test and use the 1MB or 2MB file.

Right! That's exactly what I see now, but prior to posting this, the 1MB file as well as the 2mb file were yielding me 551kbps.

How is it decreasing TCP Receive Window increased my speed?

Ah well, I won't question it. I can stream porn without interruption in WVD now.

That's really the reason for this post; The constant interruptions where it needed to re-buffer were very interfering.