zeroimpact
Active Member
I think if you really want to get accurate speed tests we need a template of some sort that everyone in the forum should follow. Because all factors needs to be taken into consideration plus a base line of testing is required.
Then once you have a baseline at which one expects to get (realistically) and then do the tests against this, then only can one really measure who has bad connection speed and who is fine. Every one is throwing speed tests around, but they do not give the methodology of testing. Plus each site one connects to is different.
(BTW P2P software is not a test to see how well your downloads are, there are just too many factors to concider.)
The Template should at least consist out of :
1.) Package type : i.e. 128,256 or 512
2.) Modem Type, Firmware as well as drivers and OS running on
3.) Connection Status (Signal,Tower etc)
4.) What type of antenna do you use.
5.) Max Transfer Rate for the package i.e 16KB for 128Kb
6.) Expected Average Transfer Rate for the package i.e 11KB for 128Kb
7.) And A Realistic Transfer Rate Depending of time of day testing is done, and how congested the internet sites are that you are testing against
8.) Step by Step Test Methodologies and sites to be tested against
9.) Check your packet losses
I’m sure with the collective knowledge of everyone in this forum (especially Rodent and ProAsm) we can put something like this together.
Then you can only moan and bitch [}
], because now you have a valid BASELINE, and with this one can then rather work proactive with Sentech to get the service at a level
Which one wants it to be at.
Maybe we should also try and find out what Sentech testing methods are as well, to see how they do validate the speeds ?
This is my 2.5 cents [
]… So lets get such a template up ?
Tower : 82 [RadioKop]
Signal : 10%
Antenna: Standard Modem Antenna
Firmare: 4.x
PacketLoss : www.Sentech.co.za = 15%
Then once you have a baseline at which one expects to get (realistically) and then do the tests against this, then only can one really measure who has bad connection speed and who is fine. Every one is throwing speed tests around, but they do not give the methodology of testing. Plus each site one connects to is different.
(BTW P2P software is not a test to see how well your downloads are, there are just too many factors to concider.)
The Template should at least consist out of :
1.) Package type : i.e. 128,256 or 512
2.) Modem Type, Firmware as well as drivers and OS running on
3.) Connection Status (Signal,Tower etc)
4.) What type of antenna do you use.
5.) Max Transfer Rate for the package i.e 16KB for 128Kb
6.) Expected Average Transfer Rate for the package i.e 11KB for 128Kb
7.) And A Realistic Transfer Rate Depending of time of day testing is done, and how congested the internet sites are that you are testing against
8.) Step by Step Test Methodologies and sites to be tested against
9.) Check your packet losses
I’m sure with the collective knowledge of everyone in this forum (especially Rodent and ProAsm) we can put something like this together.
Then you can only moan and bitch [}
], because now you have a valid BASELINE, and with this one can then rather work proactive with Sentech to get the service at a levelWhich one wants it to be at.
Maybe we should also try and find out what Sentech testing methods are as well, to see how they do validate the speeds ?
This is my 2.5 cents [
]… So lets get such a template up ?Tower : 82 [RadioKop]
Signal : 10%
Antenna: Standard Modem Antenna
Firmare: 4.x
PacketLoss : www.Sentech.co.za = 15%
!]