Wilders slow

Discussion in 'General Topics' started by ParaNodes, Sep 22, 2011.

Thread Status:
Not open for further replies.
  1. ParaNodes

    ParaNodes Registered Member

    Joined:
    Jul 15, 2003
    Posts:
    69
    Greetings,

    Last few days pages are loading really slow here(just posting this was a pain).
    Anyone else seeing this.
     
  2. LoneWolf

    LoneWolf Registered Member

    Joined:
    Jan 2, 2006
    Posts:
    3,408
    Not here, quick as always, may be on your end.
     
  3. SweX

    SweX Registered Member

    Joined:
    Apr 21, 2007
    Posts:
    6,429
    Yes, now and then I experience that here on Wilders :doubt:
    Yesterday was the first day for me, and still today I see that.

    Do you also use OpenDNS?
     
  4. vasa1

    vasa1 Registered Member

    Joined:
    May 1, 2010
    Posts:
    4,152
    Yes. Not all the time but it is noticeable.

    If the tech staff need details, I'll provide what I can (if elaborate instructions are given) :)
     
  5. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    17,875
    Location:
    New England
    Getting more information will help determine what is happening. "slow" can be caused by many things and the exact description of the slow effect people are seeing can point to the cause.

    The most telling thing here is that the forum is fast for some at the same time it is slow for others. That points to a network based problem rather than CPU or some other load issue. (If the CPU is running high, and load is backed up, then the forum would be equally slow for everyone. Since CPU is basically averaging 5% or less and UNIX load is between 0.10 and 0.35, which is nothing when you have multiple, multi-core processors, then we aren't slow from page processing/generation.)

    The thing to look for is probably packet loss and retransmissions. Doing a few pings to the forum IP address and looking at both the times and any noted lost packets, will point to the network as a root cause. From my ISP, I am seeing no packet loss and forum response times are excellent.

    My pings from New England to the forum server:

    Code:
    Friday, September 23, 2011 11:33AM
    
    Ping host 66.227.46.190
    #    Address         Host Name                                         Response Time
    1    66.227.46.190   wilderssecurity.com                               29 ms
    2    66.227.46.190   wilderssecurity.com                               22 ms
    3    66.227.46.190   wilderssecurity.com                               27 ms
    4    66.227.46.190   wilderssecurity.com                               21 ms
    5    66.227.46.190   wilderssecurity.com                               24 ms
    If someone is seeing packet loss, you can try doing a few repeated trace routes to see if it is a particular hop in the network that is bad, and causing the loss. (Don't be surprised if some hops in the trace don't respond, that's normal as some as set not to respond to pings. A tracert command will pass right over that after a short delay and pick up at the next hop.)

    My traceroute, minus the first couple that contain my IP address:

    Code:
    Friday, September 23, 2011 11:37AM
    
    TraceRoute to host 66.227.46.190
    #    Address         Host Name                                         Response Time
    
    
    4    12.83.49.60     Unavailable                                       9 ms
    5    151.164.38.190  Unavailable                                       17 ms
    6    64.208.110.73   te6-4-10000M.ar4.DCA3.gblx.net                    18 ms
    7    208.49.147.126  ip-208.49.147.126.gblx.net                        18 ms
    8    66.227.69.99    Unavailable                                       20 ms
    9                    No response from this host                        
    10   66.227.46.190   wilderssecurity.com                               24 ms
    The one at line 9 is okay, that router hop never replies to traceroutes.

    My assumption here is that there is some pattern with regard to the locations, and therefore network routes, of those who are having a problem.

    Oh, and a description of the slowness... When slow response is caused by packet loss and network route issues, the symptom is usually a page that comes down in piieces, rather then just the browser staying blank for 30 seconds and then giving a whole page all at once. That would be more load related to queuing up and waiting for your turn at the processor. "Pieces" means you'll get the page starting to display, but, have to wait as the rest of the objects (images and other items) fill in the page, sometimes very slowly. And it will vary a lot. Sometimes the objects come down in quick bunches, or even perfectly fine, but, the next click, many of the objects aren't there for XX seconds of waiting.

    Anyway, more details in the exact effect of what you are seeing will help.
     
  6. vasa1

    vasa1 Registered Member

    Joined:
    May 1, 2010
    Posts:
    4,152
    Code:
    PING 66.227.46.190 (66.227.46.190) 56(84) bytes of data.
    64 bytes from 66.227.46.190: icmp_req=1 ttl=54 time=291 ms
    64 bytes from 66.227.46.190: icmp_req=2 ttl=54 time=290 ms
    64 bytes from 66.227.46.190: icmp_req=4 ttl=54 time=292 ms
    64 bytes from 66.227.46.190: icmp_req=5 ttl=54 time=291 ms
    64 bytes from 66.227.46.190: icmp_req=6 ttl=54 time=292 ms
    64 bytes from 66.227.46.190: icmp_req=7 ttl=54 time=291 ms
    64 bytes from 66.227.46.190: icmp_req=8 ttl=54 time=292 ms
    64 bytes from 66.227.46.190: icmp_req=9 ttl=54 time=292 ms
    64 bytes from 66.227.46.190: icmp_req=10 ttl=54 time=298 ms
    64 bytes from 66.227.46.190: icmp_req=11 ttl=54 time=291 ms
    64 bytes from 66.227.46.190: icmp_req=12 ttl=54 time=289 ms
    64 bytes from 66.227.46.190: icmp_req=13 ttl=54 time=294 ms
    64 bytes from 66.227.46.190: icmp_req=14 ttl=54 time=297 ms
    64 bytes from 66.227.46.190: icmp_req=15 ttl=54 time=304 ms
    64 bytes from 66.227.46.190: icmp_req=16 ttl=54 time=291 ms
    64 bytes from 66.227.46.190: icmp_req=17 ttl=54 time=290 ms
    64 bytes from 66.227.46.190: icmp_req=19 ttl=54 time=289 ms
    64 bytes from 66.227.46.190: icmp_req=21 ttl=54 time=289 ms
    64 bytes from 66.227.46.190: icmp_req=22 ttl=54 time=295 ms
    64 bytes from 66.227.46.190: icmp_req=23 ttl=54 time=292 ms
    64 bytes from 66.227.46.190: icmp_req=24 ttl=54 time=290 ms
    64 bytes from 66.227.46.190: icmp_req=25 ttl=54 time=339 ms
    64 bytes from 66.227.46.190: icmp_req=26 ttl=54 time=300 ms
    64 bytes from 66.227.46.190: icmp_req=28 ttl=54 time=292 ms
    64 bytes from 66.227.46.190: icmp_req=29 ttl=54 time=312 ms
    64 bytes from 66.227.46.190: icmp_req=30 ttl=54 time=303 ms
    64 bytes from 66.227.46.190: icmp_req=31 ttl=54 time=295 ms
    64 bytes from 66.227.46.190: icmp_req=32 ttl=54 time=291 ms
    64 bytes from 66.227.46.190: icmp_req=33 ttl=54 time=290 ms
    ^C
    --- 66.227.46.190 ping statistics ---
    33 packets transmitted, 29 received, 12% packet loss, time 32031ms
    rtt min/avg/max/mdev = 289.464/295.699/339.838/9.809 ms
    
    I don't understand any of this! But this is from near Mumbai, India.
    I don't know how to do that ^^^
    I don't see that ^^^ The page, when it loads, loads fast, IIRC. TBH, I've been opening other tabs and coming back to the Wilders page after a while but I'll pay more attention tomorrow.
     
  7. Hungry Man

    Hungry Man Registered Member

    Joined:
    May 11, 2011
    Posts:
    9,148
    lol gonna need a looooot more info

    Have you tried on another computer? On another network? With another browser?
     
  8. vasa1

    vasa1 Registered Member

    Joined:
    May 1, 2010
    Posts:
    4,152
    I just opened six Wilders tabs as quickly as I could and I didn't find a delay as judged by the "loading" graphic disappearing pretty quickly from each tab.
     
  9. vasa1

    vasa1 Registered Member

    Joined:
    May 1, 2010
    Posts:
    4,152
    LOL? What's there to lol about? You maybe a rocket scientist. Not everyone else is. Not everyone else has multiple computers and networks and browsers.

    Anyway, the post was not directed to you but to the admin of this forum so please ...
     
  10. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    17,875
    Location:
    New England
    That's probably the heart of the problem. Since a webpage is brought down via many separate packets for each of many objects on the page, a loss of 12% means a lot of packets are not reaching you and have to be retransmitted. That can cause a big delay. Normally, packet loss should be a fairly rare thing on modern ISP networks.

    A trace route is done just like a ping, from the command prompt:

    Windows
    tracert 66.227.46.190

    UNIX
    traceroute 66.227.46.190

    Now, with the results from a traceroute, you may be able to see a single "hop" (each of the 10 lines in my traceroute above is a hop) that is the source of the lost packets. Effectively, you can do a ping to each IP address in the output from your trace route to test that specific network point. You are looking for the first one that starts showing consistent packet loss, as you work your way from your computer to the webserver here. That will be where the problem is located.
     
  11. ParaNodes

    ParaNodes Registered Member

    Joined:
    Jul 15, 2003
    Posts:
    69
    Greetings again,

    All seems back to normal today, I gave up yesterday so didn't see everyone's response but symptoms where minutes to load a page and loading in pieces if at all, tried numerous browsers, and several networks. Wilders was the only site doing this.
    West coast USA, Opendns, Verizon dsl

    HTH
     
Loading...
Thread Status:
Not open for further replies.