well, that i know, it has been slow for a while, but really slow lately, either not enough bandwidth, or server horsepower, or bad site design

Funny I saw this because when I just logged on I was thinking that it was a lot faster then usual.

it's not so much the forums either, as it is the site, and browsing the gallery

I've been finding WC page loads are pretty quick these days... but then I'm downunder in Oz, so gravity helps speed things up.

Mind you, tho, it's all uphill when uploading.

I experience an extreme slow phase a couple of weeks ago. Right now it seems to work fine again, but two weeks ago it was just crawling along.

+1   

Depends on the part of the site I'm looking at.

The forums seem a lot faster lately. The galleries are pretty intensive in terms of how much crud is on them.

I think the basic problem with WC is the code more than the underlying infrastructure. It's just a heavy site. I hope to see this change with WC 2K8.

Wow, check out hop 11 on up! Gets really slooowwwwwwwwwwww!


Tracing route to forums.wincustomize.com [38.98.152.145]

over a maximum of 30 hops:



1 1 ms <1 ms <1 ms 192.168.0.1

2 7 ms 7 ms 9 ms 73.46.160.1

3 8 ms 9 ms 9 ms ge-1-37-ur01.peru.in.indiana.comcast.net [68.86.186.113]

4 9 ms 19 ms 10 ms te-9-4-ur01.huntington.in.indiana.comcast.net [68.86.184.158]

5 9 ms 8 ms 10 ms te-9-3-ur03.main.in.indiana.comcast.net [68.86.184.153]

6 14 ms 20 ms 10 ms po-20-ur02.muncie.in.indiana.comcast.net [68.86.187.134]

7 13 ms 12 ms 13 ms po-10-ur01.muncie.in.indiana.comcast.net [68.86.187.138]

8 17 ms 13 ms 13 ms pos-0-11-0-0-ar01.indianapolis.in.indiana.comcast.net [68.86.90.170]

9 26 ms 30 ms 24 ms pos-0-1-0-0-cr01.nashville.tn.ibone.comcast.net [68.86.90.169]

10 38 ms 39 ms 36 ms pos-1-9-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.21]

11 71 ms 82 ms 74 ms pos-0-15-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.85.137]

12 323 ms 96 ms 96 ms 68.86.89.158

13 96 ms 96 ms 97 ms vl3492.mpd01.lax01.atlas.cogentco.com [154.54.3.9]

14 102 ms 96 ms 97 ms te8-4.mpd01.iah01.atlas.cogentco.com [154.54.2.197]

15 110 ms 107 ms 114 ms te7-3.mpd01.dfw01.atlas.cogentco.com [154.54.5.129]

16 109 ms 112 ms 106 ms te2-3.mpd01.mci01.atlas.cogentco.com [154.54.5.14]

17 111 ms 115 ms 107 ms te7-4.mpd01.ord01.atlas.cogentco.com [154.54.2.190]

18 117 ms 106 ms 114 ms gi12-0-0.core01.ord01.atlas.cogentco.com [154.54.1.97]

19 121 ms 109 ms 106 ms po5-0.core01.tol01.atlas.cogentco.com [154.54.5.154]

20 108 ms 112 ms 111 ms po5-0.core01.dtw04.atlas.cogentco.com [154.54.1.2]

21 109 ms 107 ms 107 ms po4-0.core01.dtw03.atlas.cogentco.com [154.54.25.61]

22 108 ms 118 ms 109 ms vl3504.na01.b015487-0.dtw03.atlas.cogentco.com [38.20.36.214]

23 109 ms 110 ms 121 ms stardock-corporation.demarc.cogentco.com [38.99.219.166]

24 111 ms 112 ms 121 ms 38.98.152.145



Trace complete.

It looks like the whole thing stalls for you the second you hit Cogent's network.  This, unfortunately, is something that is almost entirely outside of our control since the problem is on Cogent's network, and not specifically with our servers.

Same problem, things slow down as soon as they hit the cogent network.

StardockCorporation.demarc.cogentco.com is the boundary point where anything after that point is Stardock equipment.  Think of it as the property line.  Everything to one side belongs to us, everything on the other side is Cogent/someone else.

We are working on being less dependent on a single provider for our connectivity.  It's just a bit of a slow process (I was out in another datacenter on Friday for this problem)

Tracing route to forums.wincustomize.com [38.98.152.145]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 11 ms 14 ms cpe-76-167-188-1.socal.res.rr.com [76.167.188.1]
3 14 ms 13 ms 11 ms gig2-18.ontrca1-swt1.socal.rr.com [76.167.9.49]
4 10 ms 11 ms 10 ms 76.167.9.197
5 28 ms 23 ms 32 ms tge4-0-0.lsanca4-rtr1.socal.rr.com [76.167.2.76]
6 39 ms 26 ms 52 ms so-2-3-0.cr0.dfw10.tbone.rr.com [66.109.6.102]
7 16 ms 16 ms 15 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
8 50 ms 17 ms 20 ms te2-5.mpd01.lax05.atlas.cogentco.com [154.54.10.249]
9 16 ms 15 ms 17 ms vl3493.mpd01.lax01.atlas.cogentco.com [154.54.6.229]
10 30 ms 25 ms 28 ms te4-2.ccr01.sna02.atlas.cogentco.com [154.54.3.37]
11 19 ms 18 ms 18 ms te4-2.ccr01.san01.atlas.cogentco.com [154.54.25.126]
12 31 ms 28 ms 25 ms te4-2.ccr01.phx02.atlas.cogentco.com [154.54.7.85]
13 56 ms 53 ms 55 ms te4-2.ccr01.aus01.atlas.cogentco.com [154.54.1.165]
14 57 ms 54 ms 54 ms te8-2.mpd01.iah01.atlas.cogentco.com [154.54.1.66]
15 54 ms 54 ms 55 ms te7-3.mpd01.dfw01.atlas.cogentco.com [154.54.5.129]
16 64 ms 70 ms 69 ms te2-3.mpd01.mci01.atlas.cogentco.com [154.54.5.14]
17 87 ms 95 ms 86 ms te2-1.mpd01.ord01.atlas.cogentco.com [154.54.2.234]
18 82 ms 80 ms 83 ms gi12-0-0.core01.ord01.atlas.cogentco.com [154.54.1.97]
19 89 ms 85 ms 95 ms po5-0.core01.tol01.atlas.cogentco.com [154.54.5.154]
20 89 ms 87 ms 88 ms po6-0.core01.dtw04.atlas.cogentco.com [154.54.25.110]
21 89 ms 87 ms 85 ms po4-0.core01.dtw03.atlas.cogentco.com [154.54.25.61]
22 92 ms 92 ms 86 ms vl3504.na01.b015487-0.dtw03.atlas.cogentco.com [38.20.36.214]
23 94 ms 98 ms 109 ms stardock-corporation.demarc.cogentco.com [38.99.219.166]
24 90 ms 89 ms 90 ms 38.98.152.145

Trace complete.