SwingDJs.com slooow
Moderators: Mr Awesomer, JesseMiner, CafeSavoy
SwingDJs.com slooow
why is swingdjs.com so incredibly slow lately? The last week the site has been so slow I almost don't even bother using it. Takes up to 30s loading a page.
And it's only this site, every other site I visit works like normal (less than 3s load time)
And it's only this site, every other site I visit works like normal (less than 3s load time)
The ultimate european swing site!
www.heptown.com
www.heptown.com
- JesseMiner
- Posts: 1034
- Joined: Mon Nov 18, 2002 5:36 pm
- Location: San Francisco, CA
- Contact:
-
- Posts: 661
- Joined: Wed Nov 20, 2002 2:52 pm
- Location: Saskatoon, Canada
Yeah, it's been quite snappy for me too. Even from work which is often slow.
LazyP, you can probably figure out where the problem is by using a traceroute tool.
I assume you're using Windoze so here's what you do:
Open up a command prompt/DOS window.
At the prompt, type:
It will then measure the time it takes to get to each "hop" between you and the swingdjs server. Normal times shouldn't be much more than 200ms even from far away locations. The first hop with a significantly longer time indicates where the problem is.
It will also report "packet loss" which means information is getting lost. If you see any packet loss, that would also make things slow because information will have to be re-transmitted.
If the problem is one of the first few hops, contact your ISP, they are probably having issues. If it's somewhere in the middle, it's probably not something that can be easily fixed. If it's close to the end, let Jesse know and he can probably submit a trouble ticket with the hosting provider.
LazyP, you can probably figure out where the problem is by using a traceroute tool.
I assume you're using Windoze so here's what you do:
Open up a command prompt/DOS window.
At the prompt, type:
Code: Select all
tracert -d www.swingdjs.com
It will also report "packet loss" which means information is getting lost. If you see any packet loss, that would also make things slow because information will have to be re-transmitted.
If the problem is one of the first few hops, contact your ISP, they are probably having issues. If it's somewhere in the middle, it's probably not something that can be easily fixed. If it's close to the end, let Jesse know and he can probably submit a trouble ticket with the hosting provider.
- JesseMiner
- Posts: 1034
- Joined: Mon Nov 18, 2002 5:36 pm
- Location: San Francisco, CA
- Contact:
- LindyChef
- Posts: 228
- Joined: Tue Apr 01, 2003 7:52 pm
- Location: Houston and Seattle (bi-coastal wanna-be)
- Contact:
Basically it's looking at the steps it takes to get from your computer to the computer you are pinging. The ordered lines are your steps.
The three columns with ms next to them are the time it takes for each of the three pings to get from your computer to that step. The IP address listed next to the ms column is the IP of the step.
So typically what happens is the first few steps are getting from your home network through your ISP to the internet backbone ... then you go through the internet backbone and the last few steps are getting from the target's ISP all the way down to the target IP.
Hope that helps.
The three columns with ms next to them are the time it takes for each of the three pings to get from your computer to that step. The IP address listed next to the ms column is the IP of the step.
So typically what happens is the first few steps are getting from your home network through your ISP to the internet backbone ... then you go through the internet backbone and the last few steps are getting from the target's ISP all the way down to the target IP.
Hope that helps.
The "* * 489 milliseconds" line indicates that two packets of three were not returned within some amount of time, probably 5 seconds. Whoever 65.117.100.38 is, they're suffering packet loss. (I think lost packets are retransmitted until they are eventually received or a pre-set time limit expires whereupon the attempted connection fails, so a temporary disconnect is no big deal.)JesseMiner wrote:
- JesseMiner
- Posts: 1034
- Joined: Mon Nov 18, 2002 5:36 pm
- Location: San Francisco, CA
- Contact:
Thanks for the explanations. I was pretty sure of most of it, but thanks for confirming my suspicions.
The IP address in question here ( 65.117.100.38 ) is in Salt Late City, and our ISP is in Provo. But whatever this problem is, I don't see it having any significant impact on our connect as I still haven't encountered any decrease in speed when accessing the site.
Jesse
The IP address in question here ( 65.117.100.38 ) is in Salt Late City, and our ISP is in Provo. But whatever this problem is, I don't see it having any significant impact on our connect as I still haven't encountered any decrease in speed when accessing the site.
Jesse
-
- Posts: 661
- Joined: Wed Nov 20, 2002 2:52 pm
- Location: Saskatoon, Canada
My interperetation (network guru) is that the router at that address is not dropping traffic it is meant to forward since the times for subsequent hops are normal and there is no packet loss.
A common design in big iron routers is stuff like pings and ICMP messages are handled in a separate (and usually smaller) processor than "normal" routing which is usually done by a much faster specialized processor(s).
So I'd say the host CPU on the router is busy (perhaps indicating some other problem) but the good response time and lack of packet loss indicates packets are still being routed in a timely manner.
A common design in big iron routers is stuff like pings and ICMP messages are handled in a separate (and usually smaller) processor than "normal" routing which is usually done by a much faster specialized processor(s).
So I'd say the host CPU on the router is busy (perhaps indicating some other problem) but the good response time and lack of packet loss indicates packets are still being routed in a timely manner.
Well, I'm using Linux. And sitting in sweden on the fastest network available (Swedish university network, Gigabyte connection)
Results of ping www.swingdjs.com:
PING www.swingdjs.com (65.121.176.20) 56(84) bytes of data.
do_ypcall: clnt_call: RPC: Timed out
64 bytes from 65.121.176.20: icmp_seq=1 ttl=42 time=196 ms
do_ypcall: clnt_call: RPC: Timed out
64 bytes from 65.121.176.20: icmp_seq=2 ttl=42 time=200 ms
Results of traceroute www.swingdjs.com (which takes 10 seconds):
traceroute to www.swingdjs.com (65.121.176.20), 30 hops max, 38 byte packets
1 (130.235.1.3) 1.444 ms 0.878 ms 0.817 ms
2 gsec-gw-xbb.net.lu.se (130.235.8.121) 0.502 ms 0.452 ms 0.379 ms
3 malmo1-SRP2.sunet.se (130.242.85.33) 1.485 ms 1.523 ms 1.438 ms
4 vaxjo1-pos0.sunet.se (130.242.81.202) 5.581 ms 5.036 ms 5.065 ms
5 vaxjo2-POS1.sunet.se (130.242.82.166) 24.032 ms 5.101 ms 5.218 ms
6 kalmar2-POS4.sunet.se (130.242.81.129) 68.571 ms 210.006 ms 10.168 ms
7 stockholm2-POS3.sunet.se (130.242.81.122) 14.556 ms 13.401 ms 13.106 ms
8 se-kth.nordu.net (193.10.252.177) 21.392 ms 13.931 ms 13.164 ms
9 s-b4-pos2-3.telia.net (213.248.101.153) 20.981 ms 14.038 ms 13.123 ms
10 s-bb2-pos7-2-0.telia.net (213.248.66.13) 17.716 ms 13.502 ms 13.629 ms
11 kbn-bb2-pos0-0-0.telia.net (213.248.65.29) 31.299 ms 21.036 ms 21.250 ms
12 nyk-bb2-pos5-0-0.telia.net (213.248.64.34) 112.333 ms 112.178 ms 112.588 ms
13 ash-bb1-pos5-0-0.telia.net (213.248.80.138) 116.909 ms 117.313 ms 116.573 ms
14 dcp-brdr-02.inet.qwest.net (205.171.1.157) 120.423 ms 120.213 ms 120.421 ms
15 205.171.251.33 (205.171.251.33) 120.525 ms 120.502 ms 119.992 ms
16 dca-core-02.inet.qwest.net (205.171.8.221) 121.737 ms 121.684 ms 121.270 ms
17 ewr-core-03.inet.qwest.net (205.171.8.182) 120.673 ms 119.491 ms 119.126 ms
18 ewr-core-01.inet.qwest.net (205.171.17.5) 119.306 ms 119.206 ms 119.322 ms
19 kcm-core-03.inet.qwest.net (205.171.8.185) 161.099 ms 161.013 ms 160.993 ms
20 kcm-core-01.inet.qwest.net (205.171.29.121) 161.231 ms 160.732 ms 160.805 ms
21 dia-core-01.inet.qwest.net (205.171.8.137) 171.918 ms 172.703 ms 171.885 ms
22 dia-core-03.inet.qwest.net (205.171.142.22) 171.971 ms 175.415 ms 172.227 ms
23 slk-core-01.inet.qwest.net (205.171.205.93) 191.612 ms 192.399 ms 192.577 ms
24 slc-edge-02.inet.qwest.net (205.171.131.13) 191.645 ms 191.845 ms 191.561 ms
25 * 65.117.100.50 (65.117.100.50) 195.666 ms *
26 core0-sis0.npsis.com (67.136.31.22) 195.224 ms 195.183 ms 195.311 ms
Results of ping www.swingdjs.com:
PING www.swingdjs.com (65.121.176.20) 56(84) bytes of data.
do_ypcall: clnt_call: RPC: Timed out
64 bytes from 65.121.176.20: icmp_seq=1 ttl=42 time=196 ms
do_ypcall: clnt_call: RPC: Timed out
64 bytes from 65.121.176.20: icmp_seq=2 ttl=42 time=200 ms
Results of traceroute www.swingdjs.com (which takes 10 seconds):
traceroute to www.swingdjs.com (65.121.176.20), 30 hops max, 38 byte packets
1 (130.235.1.3) 1.444 ms 0.878 ms 0.817 ms
2 gsec-gw-xbb.net.lu.se (130.235.8.121) 0.502 ms 0.452 ms 0.379 ms
3 malmo1-SRP2.sunet.se (130.242.85.33) 1.485 ms 1.523 ms 1.438 ms
4 vaxjo1-pos0.sunet.se (130.242.81.202) 5.581 ms 5.036 ms 5.065 ms
5 vaxjo2-POS1.sunet.se (130.242.82.166) 24.032 ms 5.101 ms 5.218 ms
6 kalmar2-POS4.sunet.se (130.242.81.129) 68.571 ms 210.006 ms 10.168 ms
7 stockholm2-POS3.sunet.se (130.242.81.122) 14.556 ms 13.401 ms 13.106 ms
8 se-kth.nordu.net (193.10.252.177) 21.392 ms 13.931 ms 13.164 ms
9 s-b4-pos2-3.telia.net (213.248.101.153) 20.981 ms 14.038 ms 13.123 ms
10 s-bb2-pos7-2-0.telia.net (213.248.66.13) 17.716 ms 13.502 ms 13.629 ms
11 kbn-bb2-pos0-0-0.telia.net (213.248.65.29) 31.299 ms 21.036 ms 21.250 ms
12 nyk-bb2-pos5-0-0.telia.net (213.248.64.34) 112.333 ms 112.178 ms 112.588 ms
13 ash-bb1-pos5-0-0.telia.net (213.248.80.138) 116.909 ms 117.313 ms 116.573 ms
14 dcp-brdr-02.inet.qwest.net (205.171.1.157) 120.423 ms 120.213 ms 120.421 ms
15 205.171.251.33 (205.171.251.33) 120.525 ms 120.502 ms 119.992 ms
16 dca-core-02.inet.qwest.net (205.171.8.221) 121.737 ms 121.684 ms 121.270 ms
17 ewr-core-03.inet.qwest.net (205.171.8.182) 120.673 ms 119.491 ms 119.126 ms
18 ewr-core-01.inet.qwest.net (205.171.17.5) 119.306 ms 119.206 ms 119.322 ms
19 kcm-core-03.inet.qwest.net (205.171.8.185) 161.099 ms 161.013 ms 160.993 ms
20 kcm-core-01.inet.qwest.net (205.171.29.121) 161.231 ms 160.732 ms 160.805 ms
21 dia-core-01.inet.qwest.net (205.171.8.137) 171.918 ms 172.703 ms 171.885 ms
22 dia-core-03.inet.qwest.net (205.171.142.22) 171.971 ms 175.415 ms 172.227 ms
23 slk-core-01.inet.qwest.net (205.171.205.93) 191.612 ms 192.399 ms 192.577 ms
24 slc-edge-02.inet.qwest.net (205.171.131.13) 191.645 ms 191.845 ms 191.561 ms
25 * 65.117.100.50 (65.117.100.50) 195.666 ms *
26 core0-sis0.npsis.com (67.136.31.22) 195.224 ms 195.183 ms 195.311 ms
The ultimate european swing site!
www.heptown.com
www.heptown.com
- GemZombie
- Posts: 772
- Joined: Wed Nov 20, 2002 2:46 pm
- Location: Alpharetta, GA (Formerly SLO, CA)
- Contact:
That's quite a hop to get to swingdjs...
It's Gigabit (not byte, we all could wish!) btw... and has nothing to do with your universities connection to the outside world, since I hightly doubt your university uses Gigabit to connect their backbone to the outside network. Indeed it looks like your local network is fairly good (until you get to kalmar2).
Any slowness you have would likely be a result of how many hops it takes you to get to swingdjs.com... perhaps telia or qwest is having problems.
It's Gigabit (not byte, we all could wish!) btw... and has nothing to do with your universities connection to the outside world, since I hightly doubt your university uses Gigabit to connect their backbone to the outside network. Indeed it looks like your local network is fairly good (until you get to kalmar2).
Any slowness you have would likely be a result of how many hops it takes you to get to swingdjs.com... perhaps telia or qwest is having problems.
-
- Posts: 661
- Joined: Wed Nov 20, 2002 2:52 pm
- Location: Saskatoon, Canada
Hmm, response times look good and there's no packet loss except from that one hop (I'd guess it's another port on the same router Jesse saw packet loss on). I'd say the network is fine. Since nobody else is experiencing slow-ness I'd rule out the swingdjs server.
Do you find swingdjs is slow on all pages or just some?
Do you find swingdjs is slow on all pages or just some?
All of swingdsj is slow, every single page.
The swedish universities have a gigabit network through all of sweden (that's sunet.se: Swedish Universities NETwork), the server kalmar2 is far away from here (don't know the exact distance, >3 hours drive by car)
The swedish universities have a gigabit network through all of sweden (that's sunet.se: Swedish Universities NETwork), the server kalmar2 is far away from here (don't know the exact distance, >3 hours drive by car)
The ultimate european swing site!
www.heptown.com
www.heptown.com
-
- Posts: 661
- Joined: Wed Nov 20, 2002 2:52 pm
- Location: Saskatoon, Canada
Hmm, I still don't think it's the network.
Do you know if your university uses a proxy server? That's one possibility. Another possibility would be your browser rendering the site pages.
Try loading the site with images turned off in your browser. Also try loading the site in a text mode browser (lynx, links or w3m). It won't be pretty but it would measure if the page data is getting to you in a timely manner.
Do you know if your university uses a proxy server? That's one possibility. Another possibility would be your browser rendering the site pages.
Try loading the site with images turned off in your browser. Also try loading the site in a text mode browser (lynx, links or w3m). It won't be pretty but it would measure if the page data is getting to you in a timely manner.