go to http://www.gameloot.net/cgi-bin/auction.pl (http://)

and tell me if it loads slow? I'm on dial-up and it even loads too slow for me. My friend said it seemed pretty slow too...hmmm i'm using hostma t i x are they known for slow servers?

Even my www.gameloot.net page which only has one word on it says testing 123 is slow to load so i'm confused :mad:

Loads just fine for me....What happens when you do a tracert or a ping?

from the command window type

tracert yourdomain.com

and

ping yourdomain.com

dude, that site is hella-slow. :(

Pings are fine tho...must be the server.

I agree very slow, who hosts you?

yea loads pretty slow - might be the perl script though (does it have any loops)

Yup. It's real slow from Canada.

his site loads in under 7 secs on my side with cache cleard Im in Orlando Fl

It can't be the perl script because look at gameloot.net thats like 2 words and it takes 5 seconds to load lol

The trace route slowed down once it got to reach.com.

8 97 ms 96 ms 110 ms Pos6-0.chw-core2.Sydney.telstra.net [203.50.6.17
]
9 109 ms 83 ms 82 ms Pos2-0.pad-core5.Sydney.telstra.net [203.50.12.1
8]
10 137 ms 124 ms 110 ms GigabitEthernet0-0.syd-core02.Sydney.net.reach.c
om [203.50.13.250]
11 83 ms 82 ms 83 ms i-1-0.syd-core01.net.reach.com [202.84.143.133]

12 289 ms 329 ms 302 ms i-9-1.sjc-core01.net.reach.com [202.84.143.5]
13 302 ms 316 ms 315 ms 202.84.251.58
14 316 ms 330 ms 329 ms 134.159.63.62
15 260 ms 275 ms 275 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137
]
16 302 ms 288 ms 302 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
17 384 ms 385 ms 384 ms so-0-0-0.mp2.Philadelphia1.Level3.net [209.247.8
.65]
18 371 ms 371 ms 412 ms gig11-2.hsa1.Philadelphia1.level3.net [209.247.9
.34]
19 371 ms 384 ms 358 ms unknown.Level3.net [64.157.236.2]
20 412 ms 439 ms 467 ms 64.191.38.185

Trace complete.

Loads quickly for me....from Canada on High Speed Cable....not sure if it's just the time of day/low traffic or what. Good luck sorting it out!

It loads extremely slow.. for that few words... at least 5 seconds.... perhaps there's a runaway script on that server. You should email your host and ask them if there's any problems or issues with the servers, or if there's any scripts with problems.

You should also try asking them to move you to another server if that's simply cos the server was overloaded.

It's best to do all that now before your site starts, especially as you will require a cgi script. That will work even more sluggishly than a html page for sure.

around 3 sec from austria.

When you talk about a runaway script are you meaning on my site? God I hope not arghh! If it was from my site why would the html page that didn't call any script be slow too?

main page loaded instantly for me - UK

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 62.6.118.175 | home-network | * | | | | Webport Cluster Ealing |
| 1 | | 212.140.88.194 | webport-cl2-hg3.ealing.mdip.bt.net | Ealing, UK | * | 43 | x-- | BT MDIP Dynamic Address Pools and infrastructure |
| 2 | | 192.168.1.14 | - | ... | | 40 | x- | (private use) |
| 3 | | 195.99.125.166 | interconnect5-l0.ealing.fixed.bt.net | Ealing, UK | * | 41 | x- | BTnet POPs core addresses |
| 4 | | 194.72.9.245 | core2-pos4-3.ealing.ukcore.bt.net | Ealing, UK | * | 42 | x-- | Frame Relay Customer Network |
| 5 | | 194.72.9.238 | transit1-pos4-0.ealing.ukcore.bt.net | Ealing, UK | * | 40 | x | Frame Relay Customer Network |
| 6 | | 194.72.9.30 | transit2-pos9-0.washington.ukcore.bt.net | Washington, Sussex, UK | * | 133 | x-- | Frame Relay Customer Network |
| 7 | | 154.54.10.97 | p12-4.pr01.iad01.atlas.psi.net | - | | 129 | x- | 154.54.10.0 |
| 8 | | 154.54.2.249 | p1-2.core01.dca01.atlas.cogentco.com | Washington, DC, USA | -05:00 | 216 | --x-- | 154.54.2.0 |
| 9 | | 66.28.4.18 | p4-0.core01.phl01.atlas.cogentco.com | Philadelphia, PA, USA | -05:00 | 147 | -x------ | 66.28.4.0 |
| 10 | | 66.28.67.242 | g50.ba01.b003003-3.phl01.atlas.cogentco.com | Philadelphia, PA, USA | -05:00 | 154 | x--- | 66.28.67.0 |
| 11 | | 66.250.5.70 | BurstNet.demarc.cogentco.com | - | | 157 | x-- | 66.250.5.0 |
| 12 | | 66.197.191.17 | pos-6-1-border.scr1.HOSTNOC.net | | | 140 | x- | 66.197.191.0 |
| 13 | | 64.191.38.185 | www.gameloot.net | | | 141 | x | 64.191.38.0 |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


loaded instant for me2 and im UK

and average ping was 141

Originally posted by Whipsmack
When you talk about a runaway script are you meaning on my site? God I hope not arghh! If it was from my site why would the html page that didn't call any script be slow too?

Runaway script can be from anyone on the same server. If the host do not limit resources per virtual host, that can be an issue. It may be from you or it may be from others. Since your site is not even up, it is more likely to be from others. However that's not a certainty, since you had been testing that script of yours.

well thanks everyone for the help hehe it looks as if the site is back to normal speed....maybe cause its 2:30 AM lol I hope it's not slow like that again :(

yes,

is verry fast not one secound:D

zottelbaer

Took about 8 seconds for me here in Texas on wireless broadband, which is kinda high for that site on broadband. Got pings in the mid 60's though.:)

Tracing route to gameloot.net [64.191.38.185]
over a maximum of 30 hops:

1 16 ms 19 ms 19 ms 10.18.1.1
2 18 ms 19 ms 19 ms F0-1-0.G-RTR1.ALB.verizon-gni.net [141.149.4.66]
3 29 ms 19 ms 19 ms 130.81.5.1
4 29 ms 29 ms 29 ms so-0-1-1-0.CORE-RTR1.NY5030.verizon-gni.net [130.81.4.85]
5 29 ms 29 ms 29 ms so-0-2-0-0.BB-RTR2.NY5030.verizon-gni.net [130.81.8.74]
6 29 ms 28 ms 29 ms so-0-3-0-0.BB-RTR1.NY60.verizon-gni.net [130.81.8.77]
7 29 ms 29 ms 29 ms so-1-0-0-0.PEER-RTR1.NY60.verizon-gni.net [130.81.4.210]
8 29 ms 29 ms 29 ms jfk-edge-20.inet.qwest.net [65.116.172.85]
9 29 ms 29 ms 29 ms jfk-core-03.inet.qwest.net [205.171.230.18]
10 29 ms 29 ms 29 ms jfk-brdr-02.inet.qwest.net [205.171.230.25]
11 29 ms 29 ms 29 ms qwest-gw.n54ny.ip.att.net [192.205.32.169]
12 29 ms 28 ms 39 ms tbr1-p014001.n54ny.ip.att.net [12.123.3.1]
13 29 ms 29 ms 29 ms gbr6-p30.n54ny.ip.att.net [12.122.11.14]
14 29 ms 29 ms 29 ms gar2-p370.n54ny.ip.att.net [12.123.1.205]
15 39 ms 38 ms 39 ms 12.124.179.6
16 39 ms 229 ms 39 ms 64.191.38.185

Trace complete.

Ignore the verizon problem - whats up with the 229ms ping ? Site is VERY slow from home in NY ...

From a box at Rackshack:

traceroute to gameloot.net (64.191.38.185), 30 hops max, 38 byte packets
1 207.44.208.1 (207.44.208.1) 0.412 ms 0.179 ms 0.149 ms
2 207.218.223.9 (207.218.223.9) 0.408 ms 0.382 ms 0.312 ms
3 207.218.223.2 (207.218.223.2) 0.394 ms 0.346 ms 0.473 ms
4 g1.ba21.b000605-0.iah01.atlas.cogentco.com (66.28.28.209) 3.155 ms 1.602 ms 1.894 ms
5 g10-2.core01.iah01.atlas.cogentco.com (66.28.66.237) 2.182 ms 2.117 ms 1.863 ms
6 p15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46) 111.545 ms 163.963 ms 211.085 ms
7 p5-0.core01.mco01.atlas.cogentco.com (66.28.4.141) 23.559 ms 23.324 ms 23.278 ms
8 p14-0.core01.jax01.atlas.cogentco.com (66.28.4.154) 27.128 ms 58.409 ms 26.290 ms
9 p5-0.core01.atl01.atlas.cogentco.com (66.28.4.138) 33.104 ms 32.722 ms 33.254 ms
10 p5-0.core02.dca01.atlas.cogentco.com (66.28.4.162) 161.978 ms 184.646 ms 240.717 ms
11 p15-0.core01.dca01.atlas.cogentco.com (66.28.4.21) 105.076 ms 187.469 ms 223.775 ms
12 p4-0.core01.phl01.atlas.cogentco.com (66.28.4.18) 48.173 ms 48.028 ms 48.095 ms
13 g49.ba01.b003003-3.phl01.atlas.cogentco.com (66.28.67.238) 48.481 ms 48.197 ms 55.503 ms
14 BurstNet.demarc.cogentco.com (66.250.5.70) 49.145 ms 48.607 ms 48.709 ms
15 pos-6-1-border.scr1.hostnoc.net (66.197.191.17) 54.840 ms 54.890 ms 54.710 ms
16 64.191.38.185 (64.191.38.185) 55.152 ms 55.051 ms 55.047 ms

The 229 ping is probably a freak packet. Another traceroute may not show that.

I think there is noproblemwith the site.Its loading almost instanltly

yea still great loading times now