Jump to content

resopalrabotnick

News Anchor
  • Posts

    5,435
  • Joined

  • Last visited

  • Speed Test

    My Results

Posts posted by resopalrabotnick

  1. this is asking the obvious but one never knows, you arent running a p2p client in the background or any such thing, streaming video or whatever?

    just asking because that's the last thing besides a major bork on your isp or in the cable that could cause your speed to be so horrifically low.

    one other thing you can do is make sure all the connections are firmly seated. if there is any splices at your house in the cable check those. has the cable gotten pinched somewhere?

    oh, most important, have you ever reached your advertised speed?

    if so, what has changed in and around your comp or the cable since then?

    havent heard of that being a problem with cable, but maybe disconnecting tv cable receivers, if any. might be interfering with your signal. but unlikely?

    otherwise i agree with vageli. call them.

  2. hmm.

    the fact that these are averages is the problem.

    each sample there is taken over what, 10 or 15 minutes?

    if this is indeed a problem with the links bandwidth we are looking for spike with a duration of a few seconds. that is enough to bork a test if someone happens to start in that window. do you have a possibility to monitor your usage with more resolution? or realtime?

    the machine you are running sounds big enough to power a 100mbit link fully, so i really am not thinking of that. if anyone out there has an idea if it could be a problem with the config, i would be happy to be wrong about the bandwidth. but to me it sounds like the most probable reason.

    worst case: the net the server hooks into has a high load and there isn't a chance in hell that he can hit 100mbps.

    only way to check that would be to install the fix to the test i proposed and throttle it way down, until there are no more complaints.also, do you have stats on how many are really testing at any one time?

    if there is indeed a problem with the test in any way, finding it will be a major league pain in the arse, lol.

    am i glad all i need to do is kibitz.

  3. so my 25 users on the forum was pretty much accurate.

    my point is:

    user goes to testmy.net

    knocks counter up by one.

    klicks on ul or dl test.

    selects size of test.

    up to now about 15 seconds of essentially idle time have passed. average. give or take for newb / reg.

    test starts. i'll give it 15 seconds of actual data transfer. note that the higher the bandwidth used, the shorter the time of transfer!

    results show.

    user looks them over, ponders them etc.

    30 seconds.

    maybe a retest. 15 seconds data.

    compare results.

    cheer/curse

    brag to buddies on im or phone or next to him or whatever.

    at least a minute

    window stays open for reference for further action keeping counter up.

    so 2 minutes of a user being active on the site entails 30 seconds of data transfer. ill be generous and let them retest etc, give them 10 megabytes of transferred data which at average speeds will take about 60 to 90 seconds.

    and that is at 100 to 1500 kbps, meaning they don't take up much bandwidth.

    it's random spikes of users that kill individual tests.

    that's what load balancing would eliminate.

  4. well, the tech may have told you to call for a reason, i'd say you grab a sandwhich and wait out the hold, they may want to have you fiddle with their gear, meaning that the chat would die, making it impossible to give instructions.

    i mean, the guy /asked/ you to call. that would give me hope that they at least have an idea of what the prob may be.

  5. not really all that surprising. i dl at about 2800 kbps. even the 3 meg test takes me less than 11 seconds to complete.

    that's why the server side should monitor all running tests and delay the start of a test for a few seconds if there happens to be a spike. most people would probably not even reall notice a delay of a few seconds, and the advantage to queing them like this would be that everyone is guaranteed a fat chunk of bandwidth for his/her test.

    the accuracy would be much improved as a result, making sure test results are reproducable and the unknown factor of <was the link bottlenecked when i tested or did my tweaking bork mine> would be eliminated.

    i for one would be more than happy to wait a few seconds for other testers to finish so i could run a clean test. and that would then be an even better thing to advertise with. testmy.net has this awesome loadbalancing so even though it's the most fucking popular site on the planet everyone gets a fair shot at testing.

  6. from the faq:

    We do have a fast server - Dual 2.8GHz Xeon Processors, 2 GB DDR RAM, Rehat Linux, MySQL server, Apache Webserver, PHP, 100 Mbps uplink to a 12 Gbps Direct Fiber network.  TestMy.net knows what kind of server is needed to get correct test scores to all users regardless of time of day and server load.

    and i don't think, otherwise there is a lot of people with slow connects not taking up much bandwidth, that the number of users shown includes all those people reading/posting on the forum.

    only when someone throws down a challenge do they all go to test at the same time, and then get borked results. for my views on adding a short delay, dynamic, at the beginning of the test if necessary, see previous post.

  7. this would probably entail a whole and complete rewrite of the whole testing script. but what the hell.

    reserve 95mbit of the 100 mbit for the test, maybe 15 of that again for the upload.

    let the test run as long as there is at least 10 mbit available for the dl test and 2 for the upload. that way many small timers can test simultaneous, only if several fast ones are dl/ing will the script have to delay a few seconds before it starts the queued clients. the values would have to be monitored and tweaked, but 10mbit avail for down sounds like a good value to ensure that even a fast link like RTB's can stretch it's legs.

    that would also prevent getting 30 second waits, since the fast links do even the 3 meg test in 10 seconds or less, freeing the bandwidth up quickly. maybe limit number of tests per ip to 5 a day or so or maybe 30 in a week, so someone doing a lot of tweaking can run a hoopload of tests and then just has to wait a bit for his quota to fill up again.

  8. hm, i seem to have replaced my real comp skills, i hope the ones i picked up working for german telekom will do.

    first off, that ping looks good.

    which leads me to concur with the troll and the swede. lose the tweaks, check it. either you overtweaked something or something that shouldn't be fiddled with, or you have a line issue.

    on your end, unplug all phones, faxes, modems whatever. make sure you have the splitter hooked up right. if that solves your worries, your splitter is letting phone crap into the high freq part of the line dsl uses, borking you. if all the cables are ok, plugs clean, clean contacts with a soft pencil eraser if necessary, and you still have trouble, get on the horn to the telco dudes, have em check the line. a corroded connection somewhere along the line can cause bad signal/noise on the line, causing the dsl to have to correct errors a lot, causing packet loss, basically.

×
×
  • Create New...