dan@sprint.com response I got

[Mutiny32]

Originally Posted by champ052005

Your argument would hold true for the same phone models. Or different phone models with the same processor speeds.

But your argument completely falls of the rails by ignoring hardware differences. 1Ghz processor will be a crap load faster in every aspect, whether it be basic functions to internet surfing, compared to phones that don't have the 1Ghz processor.

I'm not denying that a 1GHz processor will be better able to provide a snappier interface, but when the limitation on loading a webpage is the internet connection, it is no faster.

[p-slim]

Originally Posted by Mutiny32

I'm not denying that a 1GHz processor will be better able to provide a snappier interface, but when the limitation on loading a webpage is the internet connection, it is no faster.

the limitation from the tp2 and the evo will not be the internet connection, lol. The evo will load pages about 20 secs faster then the tp2, so what do you blame that on? walk into a verizon store and play with a tp2 and an Incredible, THEY WILL NOT LOAD PAGES AT THE SAME SPEED. you will read the whole page on the incredible before the tp2 even finishes loading.

[Mutiny32]

Originally Posted by p-slim

the limitation from the tp2 and the evo will not be the internet connection, lol. The evo will load pages about 20 secs faster then the tp2, so what do you blame that on?

Not on a EvDO Rev.A connection it won't. On WiFi it won't either. A lot of that has to do with the TCP/IP stack and its settings. But even if set correctly, it still won't.

[p-slim]

Originally Posted by Mutiny32

Not on a EvDO Rev.A connection it won't. On WiFi it won't either. A lot of that has to do with the TCP/IP stack and its settings. But even if set correctly, it still won't.

my nexus WILL load faster then my tp2 on the same network. YOURE WRONG MAN.

[Mutiny32]

Originally Posted by p-slim

the limitation from the tp2 and the evo will not be the internet connection, lol. The evo will load pages about 20 secs faster then the tp2, so what do you blame that on? walk into a verizon store and play with a tp2 and an Incredible, THEY WILL NOT LOAD PAGES AT THE SAME SPEED. you will read the whole page on the incredible before the tp2 even finishes loading.

Again, you are not leveling the playing field. The Linux TCP/IP stack is much more robust than that of Windows Mobile for one, but the entire OS is a different animal. If you want to argue what will make a page load faster, I suggest you go the Linux/WebKit vs WindowsCE/IE route. I'd agree then.

[p-slim]

Originally Posted by Mutiny32

Again, you are not leveling the playing field. The Linux TCP/IP stack is much more robust than that of Windows Mobile for one, but the entire OS is a different animal. If you want to argue what will make a page load faster, I suggest you go the Linux/WebKit vs WindowsCE/IE route. I'd agree then.

you're getting to technical which doesn't prove any points. The evo will load pages faster then tp2 on the same network. The fact that it loads pages faster (no matter what the reason is) will cause users to use the phone more, because users will be happy with the speed the evo renders pages. The fact that people will like webbrowsing better will cause them to browse the web more which in turn causes more bandwith usage, whats so hard to understand?

[WarChild]

Alright guys this thread is getting off topic. Lets keep it on track! Thanks for understanding.




CW

[gTen]

Originally Posted by Mutiny32

Again, you are not leveling the playing field. The Linux TCP/IP stack is much more robust than that of Windows Mobile for one, but the entire OS is a different animal. If you want to argue what will make a page load faster, I suggest you go the Linux/WebKit vs WindowsCE/IE route. I'd agree then.

Mutiny32 you are somewhat mistaken..while it is true that a stack plays a difference the bottleneck is the CPU..aside from the obvious that it is processed by the cpu..

Let me explain why..I have a TP2 and I load a web page on the TP2, the TP2 without the 2d acceleration and etc makes the 528mhz cpu process all the gzip, 16 threads of processing, images, javascript and all other graphical rendering

On my laptop though when tethering on the TP2, my cpu only processes wifi and incoming packets..but images and webpages load fast. (because all the processing is now done by my laptop)

You can actually tell the difference by doing a ping from a tethered laptop and you will get the ping, this ping already includes the tcp/ip stack. To note though latency on 3g is not the best to begin with but 4g is better

The only difference is I am not 100% sure if it just forwards all packets or does a checksum on the tcip packets (have to actually see the code to tell) but either way checksum is effected by the CPU.

on side note, yes obviously the webkit is superior to IE and Android is lighter on the CPU over windows. But this in no way effects the bigger picture.

[champ052005]

Originally Posted by Mutiny32

Again, you are not leveling the playing field. The Linux TCP/IP stack is much more robust than that of Windows Mobile for one, but the entire OS is a different animal. If you want to argue what will make a page load faster, I suggest you go the Linux/WebKit vs WindowsCE/IE route. I'd agree then.

Hmm....so from what I understand...if we compare a My Touch 3G on t-Mobile and a N1 on t-mobile, you are saying that they should load at the same time? Since they both have the same OS and the Linux TCP/IP stack?

PSlim...you are on T-Mobile...make it happen! lol.

I'm just interested to see what would happen. If Mutiny is right, then I guess I learned something new for the day lol.

I would think that RAM would be a factor too.

[Cicatrize]

Originally Posted by champ052005

Hmm....so from what I understand...if we compare a My Touch 3G on t-Mobile and a N1 on t-mobile, you are saying that they should load at the same time? Since they both have the same OS and the Linux TCP/IP stack?

PSlim...you are on T-Mobile...make it happen! lol.

I'm just interested to see what would happen. If Mutiny is right, then I guess I learned something new for the day lol.

I would think that RAM would be a factor too.

Yep, RAM is also a bottleneck for two reasons. First is allocated memory allowed for the browser, second is the bus speed. Mutiny is not right. I would bet money on it. I cannot count how many videos I've seen of different devices loading pages on the same wi-fi connection with very different results. This isn't rocket science, and if Mutiny really "does this for a living", then he should know that.