Shop OBEX P1 Docs P2 Docs Learn Events
Server Slowness? — Parallax Forums

Server Slowness?

Bruce BatesBruce Bates Posts: 3,045
edited 2008-12-10 19:00 in General Discussion
Has anyone else noticed that the server seems to be bogged down right now (9:58 AM EST, 04 DEC 2008). I DO have a dial-up link, but I can't imagine that it should take over 30 seconds to post a private message. Am I being overly critical here?

UPDATE ALL messages are taking that long to be posted!

Regards,

Bruce Bates

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
When all else fails, try inserting a new battery.

Post Edited (Bruce Bates) : 12/5/2008 9:23:00 PM GMT

Comments

  • Beau SchwabeBeau Schwabe Posts: 6,568
    edited 2008-12-04 16:31
    Bruce Bates,

    If you are using a dial-up, then it is very unlikely that the server is causing a bottleneck.

    It could be noise in the phone line... what is the weather doing in your area?
    What kind of phone line do you have?

    Years ago (10+) it was common to contact your Telephone provider and indicate to them if you were using the line for Data as well as Voice.· There were supposedly "cleaner" lines that could be used to increase the bandwidth in certain circumstances.· The add-on filters really aren't that effective unless you know exactly what frequencies you are sending/receiving.· Even then most modems already have adequate filtering... adding an external filter may only slightly increase your signal to noise ratio, but it could make it worse if improperly tuned.
    ·

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Beau Schwabe

    IC Layout Engineer
    Parallax, Inc.
  • Bruce BatesBruce Bates Posts: 3,045
    edited 2008-12-05 10:25
    Hi Beau -

    Right now it's taking a variable amount of time. In one case it took 7 seconds to post a reply. On the next occasion it took 20 seconds. The first time (7 seconds) is right on the money. Why does it now take 20 seconds (down from 30 seconds)?

    Are the routers and other paraphernalia between the East coast and the West coast that bogged down?

    To answer your questions:

    If not the server, where is the bottleneck?

    A nominal amount of noise is to be expected on any voice grade line. In all your travels, you MUST have used a laptop in a hotel with a dial-up line to Parallax, or don't you log in when you're away from work? How long would you estimate it takes your laptop to post a message?

    I DO have some nominal amount noise on my line occasionally, but that's what CRC codes are all about, or so I'm told.

    The weather is crisp and clear, about 27 degrees F in the early mornings, and 48 degrees F around noon. Aren't you glad you live in California now?

    My phone line is a plain, voice grade line. No echo suppressors, no filters, nothing but the run of the mill POTS line. I think you cable/DSL/satellite/networked folks are spoiled!

    As you say the filters (except on a DSL line) are just about worthless. The DSL filters are going for a dime apiece at some of the electronics surplus houses on the web - how good can they be for ten cents?

    Where does that leave us with the original question? Does 20-30 seconds per post, or a rough average of 17 seconds sound reasonable to you? I feel like it should be more like the 7 second post every time. Is that too high an expectation?

    Regards,

    Bruce Bates

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    When all else fails, try inserting a new battery.
  • Beau SchwabeBeau Schwabe Posts: 6,568
    edited 2008-12-05 16:44
    Bruce,
    "Are the routers and other paraphernalia between the East coast and the West coast that bogged down?" - Try this command from a DOS prompt (Start-->Run-->[noparse][[/noparse]Open:]... cmd)
    tracert forums.parallax.com
    ...This will give you an idea where your internet connection is being routed.· I get about 330ms total hop time when I do the above command.
    "If not the server, where is the bottleneck?" - The server is an unlikely candidate since under normal conditions it can keep up with very high speed connections.· If you have DSL, your bandwidth could vary depending on what time of day it is and when other people are on-line in your DSL area.· The "weak" link is going to be the slowest connection, and in most cases will be the modem or the lines running to your telephone provider.
    "In all your travels, you MUST have used a laptop in a hotel with a dial-up line to Parallax, or don't you log in when you're away from work?" - Usually I stay in a hotel that has a wireless connection, but since I telecommute about 1300 miles to Parallax on any other day, I have a constant connection to Parallax all of the time.
    "How long would you estimate it takes your laptop to post a message?" - Usually a couple of seconds.
    "I DO have some nominal amount noise on my line occasionally, but that's what CRC codes are all about, or so I'm told." - The CRC check is mainly just to determine that the data packet is error free, it is not designed to correct any errors.· If the data packet does contain errors then a request is made to send the data packet again.· After "X" number of attempts the communication is dropped.
    "Does 20-30 seconds per post, or a rough average of 17 seconds sound reasonable to you?" - No, that seems very slow, but again line noise can be a big factor.· Just for kicks, can you try a different phone line closer to your service box?
    "I feel like it should be more like the 7 second post every time. Is that too high an expectation?" - ...Or even better than 7 seconds, it depends on your modem speed.

    Edit: Another culprit to slow data speeds could be virus related ... have you done a recent scan with the latest AV-deck?· If that's not the case have you recently installed any new software that might be running in the background that you may not be aware of?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Beau Schwabe

    IC Layout Engineer
    Parallax, Inc.

    Post Edited (Beau Schwabe (Parallax)) : 12/5/2008 5:26:10 PM GMT
  • Bruce BatesBruce Bates Posts: 3,045
    edited 2008-12-05 17:58
    Beau -

    Thank you for the most considered response. Here are the answers to the questions in the order that you posed them:

    I'll be happy to run a trace route. NOT a problem. Sam Spade can do that!

    Here are the results with MULTIPLE RUNS of Tracert: NO RESPONSE!!
    I suspect this is the OFFENDING ROUTER: gigE-0.border0.vosn.net (209.151.64.2)

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    When all else fails, try inserting a new battery.
  • Bruce BatesBruce Bates Posts: 3,045
    edited 2008-12-05 18:34
    Beau -

    I continue here, in this message, because the forum "took off" on me when I tried to do a PASTE.

    That router (from the last message) has been DOWN for at least 24 hours. It's located in Colorado, which is why I suspect it's the correct one. However, there are 3-4 other routers across the US which are ALSO DOWN. I suspect it's these ROUTERS, and not my dial-up line. What do you think?

    As I mentioned earlier,·ours is a plain old telephone system·(POTS) line, like that which one might have in a house. The SWITCH is too far away for us to get DSL connectivity. I WISH we could get DSL!

    Regarding the T1 (??) line, Ken is WAY too GOOD to you :-)

    You better get that T1 line CHECKED! :-)

    CRC errors may not kill an UPLOAD (my case) or a download, but I can't believe·it wouldn't give SOME indication at either my end or the Parallax end. What do you think?

    Our phone terminal (the NIC·to the TELCO line) is almost in our back yard. The SWITCH (ESS) is MUCH farther away. I'm not sure which one you're speaking about. Which one were you speaking about?

    I would·estimate that my average baud rate is around 43·kbps for an UPLOAD and 46 kbps for a download, all other things being equal.

    Windows XP Firewall, active SPYBOT, and active Norton Anti-Virus team up to guard the DOOR. I'm NOT without more protection than most probably have! All are up-to-date.

    Thanks for your continued concern. It's not all that important that we continue this thread, unless you would choose to. I'm reasonably convinced that one of the DEAD routers is the cause of these unconscionable delays. I didn't realize that re-routing around a DOWNED server took that long <shrug>.

    NOTE: (After posting this - via "Preview before posting") - The speed is right where I would expect it to be - about 3 seconds or so! FANTASTIC!

    Regards,

    Bruce Bates



    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    When all else fails, try inserting a new battery.
  • Beau SchwabeBeau Schwabe Posts: 6,568
    edited 2008-12-05 19:00
    Bruce,

    I would also suspect the dead router in Colorado is causing a problem.

    Here is an interesting site that I found, but it sounds like you already have most of the information provided there.

    www.internettrafficreport.com/namerica.htm


    "Regarding the T1 (??) line, Ken is WAY too GOOD to you smile.gif You better get that T1 line CHECKED! smile.gif" - I use a standard cable internet provider through COX communication. If I'm using a VPN connection directly into Parallax my speed is much greater than 330ms ... more like 50ms. Thanks though.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Beau Schwabe

    IC Layout Engineer
    Parallax, Inc.
  • Bruce BatesBruce Bates Posts: 3,045
    edited 2008-12-05 21:01
    Hi Beau -

    Thanks for your response.

    It's been said that "Great minds think alike". Whether that's true in my case, I really couldn't say smile.gif
    Why? That's EXACTLY the web site I use as well!

    Do you have to water cool that VPN line? smile.gif

    Regards,

    Bruce Bates

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    When all else fails, try inserting a new battery.
  • BradCBradC Posts: 2,601
    edited 2008-12-10 08:05
    Just a quick "me too". The connection to the Parallax forums has been shocking from the UAE, Australia and the UK for me in the last 2 weeks. Today it's driving me completely nuts. It can take up to 20 seconds just to reload a forum page. I'm natively based in the UAE, but I've tried it via VPN from both Perth, Western Australia and London, UK.

    Ordinarily I'd look at my own connection, but I have 25 other web pages open from various locations and none of those take more than about 3 seconds to completely reload.

    I did have a good run last night where the Parallax forums behaved fairly well, but it's back to "flip a coin to decide if the connection times out" time again.

    traceroute from my pc locally

    brad@bklaptop2:~$ traceroute-nanog forums.parallax.com
    traceroute to forums.parallax.com (67.104.29.60), 30 hops max, 40 byte packets
     1  192.168.20.1 (192.168.20.1)  0.461 ms  0.458 ms  0.433 ms
     2  172.30.0.29 (172.30.0.29)  0.890 ms  0.945 ms  0.732 ms
     3  213.42.8.55 (213.42.8.55)  29.185 ms  36.192 ms  29.936 ms
     4  213.42.9.97 (213.42.9.97)  91.376 ms  130.876 ms  79.571 ms
     5  194.170.0.142 (194.170.0.142)  96.587 ms  41.062 ms  40.908 ms
     6  195.229.1.193 (195.229.1.193)  32.699 ms  32.498 ms  32.717 ms
     7  195.229.1.169 (195.229.1.169)  35.120 ms  40.720 ms  71.379 ms
     8  195.229.0.118 (195.229.0.118)  170.675 ms  280.508 ms dxb-emix-ra.so100.emix.ae (195.229.0.234)  200.731 ms
     9  195.69.145.200 (195.69.145.200)  260.672 ms  302.984 ms *
    10  * * p5-1-0d0.rar1.amsterdam-nh.nl.xo.net (71.5.174.9)  274.957 ms
    11  p7-0-0d0.rar2.washington-dc.us.xo.net (65.106.0.126)  254.008 ms  251.116 ms  240.646 ms
    12  * p0-0-0d0.rar1.washington-dc.us.xo.net (65.106.1.13)  253.770 ms  276.896 ms
    13  * p1-0-0.rar1.sanjose-ca.us.xo.net (65.106.0.38)  303.032 ms *
    14  * * p0-0-0d0.mar1.roseville-ca.us.xo.net (65.106.5.202)  316.259 ms
    15  207.88.80.74.ptr.us.xo.net (207.88.80.74)  334.382 ms * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    
    



    Traceroute from a co-located server in the UK

    root@bkcuk001:~# traceroute forums.parallax.com
    traceroute to forums.parallax.com (67.104.29.60), 30 hops max, 40 byte packets
     1  gw0-sov.mythic-beasts.com (93.93.128.1)  0.286 ms  0.269 ms  0.240 ms
     2  po1-1379-cr0.thn.uk.as6908.net (78.41.155.121)  0.640 ms  0.649 ms  0.640 ms
     3  g3-1.ir1.london-en.uk.xo.net (78.41.155.190)  0.579 ms  0.537 ms  0.537 ms
     4  p5-0-0d0.rar1.london-en.uk.xo.net (71.5.174.133)  0.885 ms  0.858 ms  0.885 ms
     5  p1-0-0d0.rar1.nyc-ny.us.xo.net (65.106.0.118)  68.378 ms  68.391 ms  68.476 ms
     6  p0-0-0d0.rar2.nyc-ny.us.xo.net (65.106.1.2)  68.703 ms  68.737 ms  68.727 ms
     7  p6-0-0.RAR1.Washington-DC.us.xo.net (65.106.0.2)  83.546 ms  83.608 ms  83.600 ms
     8  p1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.0.38)  156.867 ms  156.794 ms  156.804 ms
     9  p0-0-0d0.mar1.roseville-ca.us.xo.net (65.106.5.202)  159.626 ms  159.666 ms  201.608 ms
    10  207.88.80.74.ptr.us.xo.net (207.88.80.74)  159.736 ms  159.526 ms  159.523 ms
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    
    



    Now, let's press "Submit" (after copying the entire post to the clipboard in case it times out and then the submit button is broken after going "back") and see if it manages to even post.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Cardinal Fang! Fetch the comfy chair.
  • Phil Pilgrim (PhiPi)Phil Pilgrim (PhiPi) Posts: 23,514
    edited 2008-12-10 19:00
    The traceroute probably won't tell you much. It hangs up at ptr.us.xo.net from here in the States, too. It always has in my experience; and, consequently, I've never seen a complete traceroute to the forum server. But I'm getting snappy response from the forum, just the same.

    -Phil
Sign In or Register to comment.