???
bugger all diff between wireless and cable just did mine.........wireless ping 19 ms download 2.75 mbps u/l 0.89 mbps
cable ping 17.... 2.89... 0.80
im in Perth with IInet......have Belkin wireless and cable both from IInet
Last edited by HILLVIEW103; 07-04-15 at 12:41 PM.
Look Here -> |
???
If u want to go on an expedition get a Land Rover, if u want to come home from an expedition get a Landcruiser!
Yep, i have no idea what your first post is about
Wireless?? Do you mean Mobile Data speeds or do you mean the Wireless in your House?
Last edited by ol' boy; 07-04-15 at 12:54 PM.
If u want to go on an expedition get a Land Rover, if u want to come home from an expedition get a Landcruiser!
dare say the OP has been to speedtest.net Wfi V's Ethernet connection.
The result a "PING" provides is a random value, little meaningful. Run "PING" time-shifted, and you'll see what I mean.
Simply call the principle of "PING" in the memory, which is resembling a table tennis game. The left paddle is your computer, right is a server the website X. Our ping pong ball stands for a data package, which is to be sent forth and back. The ping time ( Round-Trip-Time - RTT ) is the amount of time the ball requires for one back and forth. Of course, this is an extremely simplified model. The ping pong ball takes quite a few detours in reality. The detour is mostly never the same, it's more or less random. Sometimes a data pack can be sent over servers in the United States, sometimes it can be sent over servers in France, etc. Has something to do with the bandwidth balance. Therefore, the noticeable differences in measurements results.
If you run a small batch file like this
you can watch the differences in values returned by "PING" when doing a time-shifted ping on AUSTECH from your computer.Code:@echo off set ip_server=209.188.84.6 & rem This is austech.info if not "%1"=="" goto %1 start /b %~nx0 2 start /b %~nx0 3 :1 echo Pinging AUSTECH loop 1 ping %ip_server% -n 3 timeout 10 > nul goto 1 :2 echo Pinging AUSTECH loop 2 ping %ip_server% -n 2 timeout 10 > nul goto 2 :3 echo Pinging AUSTECH loop 3 ping %ip_server% -n 2 timeout 10 > nul goto 3
Last edited by jwoegerbauer; 07-04-15 at 06:46 PM. Reason: img added
Last edited by ol' boy; 07-04-15 at 09:54 PM.
If u want to go on an expedition get a Land Rover, if u want to come home from an expedition get a Landcruiser!
Now I'm really surprised: you measure your machine's "computer speed" by means of "PING" command, which normally is used to measure "network speed". A Nobel Prize worthy measurement method!
If you want to know your "network speed", and you are on a "Windows 8.x machine, then install Microsoft's Network Speed Test (Windows-8-App) - it's free of charge.
More info:
Last edited by jwoegerbauer; 08-04-15 at 01:19 AM. Reason: typos
I guess you are referring to the computer’s processing speed. For me computer speed is dependent on 4 factors: Processor Speed, Disk Speed, Internet Speed and Graphics Processing.
BTW: Your computer seems to be a lame duck - 2.4 MHz. Today a computer's processor speed is 2.4 GHz and up to 3.7 GHz
To measure network speed (regardless whether cabled or wireless) within your LAN (i.e. from machine's NIC to AP) you simply ping your cable modem / wireless modem NIC IP. This is after the localhost the second network that connects to your computer, and is a subnet of your cable / wireless provider. For example on my wireless connection "PING" reports <1ms. So faster than the speed of light. The connection "NIC to AP" in no case is a bottle neck. If I ping AUSTECH ( 209.188.84.6 ) then "PING" reports ~178ms.
Last edited by jwoegerbauer; 08-04-15 at 05:16 AM.
Bookmarks