Check my Crazy Speeeeed !

G

GuRu

Senior Member
Joined
Mar 12, 2005
Messages
812
Reaction score
0
Location
Free Electrons
I think my UTD is suffering a major power surge ! :D

Date: 23/05/2005
Time: 13H35
Download time: 0.14 seconds
Size of file: 500 KiloBytes
Estimated line speed: 29142.9 (kilobits/second)
Estimated line speed: 3571.4 (kiloBytes/second)
 
or...... the dynamic test page at telkom didn't include the 500KB (well technically its closer to 430KB) data during the speed test, which means you loaded the page instantly causing the java script to execute instantly and display the test results for a 18KB page but whilst assumign the page was infact 500KB, that happened to me before, either they had an ASP exeption or you caught them as they were updating code :(
 
The joke is

that the page took something like 7 minutes to load and i had it was the first test I had run since switching on the computer (everything gets switched off at the wall)
 
actually you know what that sounds liek to me... the WBS cache. Whenever pages get stuck at the waiting for whatever.com bit it seems to be cache but sometimes before it times out and shows that WBS error it comes through and shows soem cached content which I need to force to reload.

I wanna know if a page send a modified header of some dat in the past does WBS still cache it? because they shouldnt, thats the rule but I think they do, I think they dont look at the http headers but rather the meta tag within a page, which sucks because hardly anyone uses those and it means theres no way to force a download reload if it isnt a HTML/XHTML page
 
Sounds Like your cache .. page timed out and loaded from your cache. Same happens when you visit the site after choosing the option to work offline.
 
sorry im not trying to be abrasive but you totally made that up. NO browser at all makes requests and if they time out uses internal cache, the reason is because if they did the user would be under the impression he was seeing a page on the net rather than a copy on thier harddrive, if you select work offline thats a diff story because then it doesn't even make the request it just loads the page from your cache if it is cached. Also it wouldn't have taken 7 minutes it would have taken 30 seconds because thats the max timeout for most browsers
 
Slim ..... that is exactly how it happened and it is not fabricated or altered in any way. If a spade is a spade then that is what it is just like my sig says. " Just stick to the facts.!"
I keep a log of all my speed tests every time i log on just for future ref. in case i decide to change to some other form of internet access, so if you want a copy of that i will send it to you for perusal at your own lesuire. :cool:
 
I am not claiming that my connection was or is running at that speed, merely posting what crazy results i got.... nothing more , nothing less other people out there can take this as an example that speed tests can give you incorrect results, so this should serve as means to keep the uninformed , informed
 
GuRu said:
I am not claiming that my connection was or is running at that speed, merely posting what crazy results i got.... nothing more , nothing less other people out there can take this as an example that speed tests can give you incorrect results, so this should serve as means to keep the uninformed , informed
Click to expand...

heh heh heh...
 
I didn't just make that up I came to that conclusion (I also said it sounds like not it is).
It cannot be the proxy or wbs cache because this would still go through the UTD.
And the UTD cannot go to speeds of 29mb/s
that is 29X the shaped 1mb or as you would think 7x4mb the max you found the modem to go to?

So if it isn't wbs cache and its not the local browser cache then wat is it?

GURU is this pc connecting through another (ICS or maybe a router)
 
its a javascript test it can still go through the utd and only evaluate the page when it is loaded as one chunk meanign the timer that starts and ends almost instantly and the code with the equation to work out the average speed per second would be off. You are thinking of this from a server side stand point assuming the timers were loaded when they should be meaning if it comes through the utd it means it was extra fast when really it could have come down incredibly slow (cached or not) and then evaluated the script in one chunk (happens all the time with java script timers actually which is why in web development we use javascript timers as a rough indication and server side timers as an absolute)

its just a javascript hiccup, nothing more nothing less, i don't think he posted it as a problem he wanted fixed, rather as a "hey look at this quirk" type thing, i mean with the way they structure thier code if the first timer isn't evaluated as you recieve it then you can download the page at 1KB/s and it would still say you have a 100mbit line.

also i never said the modem's theoretical speed was 4mbit

Anyways
 
Well anyways the page should not be allowed to be loaded as a chunk. I haven't heard of this before but there is allways a first time.

I was responding to your comment
actually you know what that sounds liek to me... the WBS cache.
Click to expand...

This Topic was a problem I wanted 'fixed' in my mind, I am very stubborn in ways of thinking. - Sorry
 
i didnt mean loaded as in downloaded, i meant drawn in the browser and during that time javascript evaluating, it happens all the time, it happened with me when i clicked the link to come to this page, not downloaded as one chunk, executed as one chunk, like i said it wouldnt matter how long it took to download if this is the case.

Just an educated guess but truth is it could have been anything, none of us know for sure, maybe it was a server side problem
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X