DriverHeaven Slow lately?

CherryPopper · Feb 26, 2003, 05:23 PM

Is it me or has the loading times for Driverheaven pages been much slower recently? I remember Zardon posting a while ago that loading times may increase since Driverheaven was hosting for Omega's new driver set, but i would expect that load to be a lot less now.

Zardon · Feb 26, 2003, 05:39 PM

Well I certainly cant say im seeing it myself, but too many people are mentioning it for it to be one individuals machine or ISP causing problems.

We have some forum problems atm, but I cant see how they are related to speed problems as server load is very low, so its not that which is causing the issues.

im looking into it and im in talks with the adminstration staff. it may be a problem along some carrier line atm.

sorry for any inconveniences.

CherryPopper · Feb 26, 2003, 05:53 PM

No problem.... thanks for the update Zardon.

Zardon · Feb 26, 2003, 06:15 PM

no I really am sorry its slow, im doing all I can, but I really dont know why it is for some people. the server location is texas, and im hearing from them there may be some outages over the coming days some maintenance on the time warner line. so lets leave it for until the weekend and see how it goes from there. server load is really low and our T3 line is more than capable of coping with our hits.

digitalwanderer · Feb 26, 2003, 07:34 PM

It ain't the connection speed, but rather the time it takes the server to process the request and serve up the info...if'n that'll help you out any.

DriveEuro · Feb 27, 2003, 12:47 AM

It's been noticeably slower to me too.... Eh who cares though.... Still quick enough.

fornicatarachnid · Feb 27, 2003, 01:26 AM

mmmmm, interesting new sig Dig, what does it mean ?

The_Neon_Cowboy · Mar 2, 2003, 01:52 AM

Hey I have got a bain sTorm!!!! (scary I know) lets all run neotrace and post the info here (minus our IP's of couse)... then we can see if its a certin path the our data is takeing couseing the problems or the sever!

couse its not on my end...............
http://www.toast.net/performance/res...loadtime=1.051

digitalwanderer · Mar 2, 2003, 02:55 PM

It's getting slower....slowly but surely I'm noticing it take longer every day to serve up me pages.

BWX · Mar 2, 2003, 03:16 PM

Quote:

Originally posted by The_Neon_Cowboy
Hey I have got a bain sTorm!!!! (scary I know) lets all run neotrace and post the info here (minus our IP's of couse)... then we can see if its a certin path the our data is takeing couseing the problems or the sever!

couse its not on my end...............
http://www.toast.net/performance/res...loadtime=1.051

Tracing route to 208.62.23.150 over a maximum of 30 hops

1 10 ms 10 ms 8 ms ##.###.##.#
2 9 ms 9 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65]
3 7 ms 9 ms 9 ms 64.8.1.206
4 7 ms 9 ms 10 ms unk-426d0125.adelphiacom.net [66.109.1.37]
5 21 ms 19 ms 18 ms unk-426d00d9.adelphiacom.net [66.109.0.217]
6 22 ms 21 ms 19 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138
7 22 ms 33 ms 20 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10]
8 23 ms 23 ms 23 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [16
9 20 ms 21 ms 19 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.
10 24 ms 22 ms 22 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161]
11 23 ms 22 ms 23 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10]
12 21 ms 21 ms 22 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42]
13 22 ms 19 ms 24 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21]
14 46 ms 46 ms 47 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109]
15 38 ms 40 ms 38 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78]
16 72 ms 55 ms 56 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82]
17 82 ms 58 ms 56 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137]
18 55 ms 53 ms 54 ms bs-mia-gw2.customer.alter.net [65.208.86.130]
19 56 ms 54 ms 54 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19]
20 52 ms 57 ms 56 ms 65.83.237.9
21 57 ms 55 ms 55 ms 205.152.144.89
22 * * * Request timed out.
23 70 ms 79 ms 58 ms 208.62.23.150

Some of my pages take up to 20 seconds to load every single time. I just try to have a few more websites open so I don't have to stare blindly at the screen. It is mainly when I am posting or when I hit the back button. But other pages (like the main pages are instant. I am stumped. I will delete ALL my cookies and clear out all my restricted spyware sites that I don't accept cookies from just to make sure, (valueclick, doubleclick,hitbox, etc........) but by the sounds of it, it's just PARTS of this site I am having the major problem with- so I don't know how that could be on my end, but I suppose anything is possible.

My average ping to this site it 54ms and my average download speed to the internet in general is 2600k to 3000k/sec. Most sites all work (basically) instantly. Some are a little slower than others of course.

Zardon · Mar 2, 2003, 03:22 PM

For an experiment try an alternative browser. I wish I could reproduce this. I cant on any computer or connection ive tried. and I know for a fact server loads are almost zero.

BWX · Mar 2, 2003, 03:25 PM

well, here it is again- I get the same timout on the same hop every single time. Maybee this is normal- I really have no idea. Maybe someone that knows can see something here.

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\*******\****~*******>ping driverheaven.com

Pinging driverheaven.com [208.62.23.150] with 32 bytes of data:

Reply from 208.62.23.150: bytes=32 time=56ms TTL=238
Reply from 208.62.23.150: bytes=32 time=60ms TTL=238
Reply from 208.62.23.150: bytes=32 time=58ms TTL=238
Reply from 208.62.23.150: bytes=32 time=56ms TTL=238

Ping statistics for 208.62.23.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 60ms, Average = 57ms

C:\*******~1\******~*****>tracert 208.62.23.150

Tracing route to 208.62.23.150 over a maximum of 30 hops

1 10 ms 10 ms 8 ms 10.0.196.1
2 9 ms 9 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65]
3 7 ms 9 ms 9 ms 64.8.1.206
4 7 ms 9 ms 10 ms unk-426d0125.adelphiacom.net [66.109.1.37]
5 21 ms 19 ms 18 ms unk-426d00d9.adelphiacom.net [66.109.0.217]
6 22 ms 21 ms 19 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138]
7 22 ms 33 ms 20 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10]
8 23 ms 23 ms 23 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193]
9 20 ms 21 ms 19 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17]
10 24 ms 22 ms 22 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161]
11 23 ms 22 ms 23 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10]
12 21 ms 21 ms 22 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42]
13 22 ms 19 ms 24 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21]
14 46 ms 46 ms 47 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109]
15 38 ms 40 ms 38 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78]
16 72 ms 55 ms 56 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82]
17 82 ms 58 ms 56 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137]
18 55 ms 53 ms 54 ms bs-mia-gw2.customer.alter.net [65.208.86.130]
19 56 ms 54 ms 54 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19]
20 52 ms 57 ms 56 ms 65.83.237.9
21 57 ms 55 ms 55 ms 205.152.144.89
22 * * * Request timed out.
23 70 ms 79 ms 58 ms 208.62.23.150

Trace complete.

C:\********~1********>ping driverheaven.com

Pinging driverheaven.com [208.62.23.150] with 32 bytes of data:

Reply from 208.62.23.150: bytes=32 time=57ms TTL=238
Reply from 208.62.23.150: bytes=32 time=67ms TTL=238
Reply from 208.62.23.150: bytes=32 time=59ms TTL=238
Reply from 208.62.23.150: bytes=32 time=57ms TTL=238

Ping statistics for 208.62.23.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 67ms, Average = 60ms

C:\*******1\*****~*******>tracert 208.62.23.150

Tracing route to 208.62.23.150 over a maximum of 30 hops

1 9 ms 9 ms 10 ms 10.0.196.1
2 9 ms 8 ms 12 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65]
3 11 ms 12 ms 12 ms 64.8.1.206
4 7 ms 9 ms 8 ms unk-426d0125.adelphiacom.net [66.109.1.37]
5 26 ms 19 ms 24 ms unk-426d00d9.adelphiacom.net [66.109.0.217]
6 20 ms 22 ms 19 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138]
7 21 ms 24 ms 42 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10]
8 21 ms 20 ms 19 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193]
9 22 ms 19 ms 21 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17]
10 22 ms 24 ms 25 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161]
11 23 ms 23 ms 20 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10]
12 20 ms 24 ms 23 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42]
13 23 ms 25 ms 22 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21]
14 47 ms 44 ms 44 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109]
15 40 ms 38 ms 37 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78]
16 57 ms 54 ms 54 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82]
17 56 ms 55 ms 54 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137]
18 53 ms 54 ms 60 ms bs-mia-gw2.customer.alter.net [65.208.86.130]
19 55 ms 53 ms 56 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19]
20 56 ms 54 ms 54 ms 65.83.237.9
21 54 ms 54 ms 52 ms 205.152.144.89
22 * * * Request timed out.
23 59 ms 73 ms 59 ms 208.62.23.150

Trace complete.

C:\******~1\*******8~******>tracert 208.62.23.150

Tracing route to 208.62.23.150 over a maximum of 30 hops

1 13 ms 7 ms 9 ms 10.0.196.1
2 6 ms 6 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65]
3 9 ms 9 ms 9 ms 64.8.1.206
4 9 ms 12 ms 9 ms unk-426d0125.adelphiacom.net [66.109.1.37]
5 20 ms 21 ms 19 ms unk-426d00d9.adelphiacom.net [66.109.0.217]
6 20 ms 24 ms 26 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138]
7 26 ms 35 ms 22 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10]
8 22 ms 25 ms 22 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193]
9 21 ms 22 ms 19 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17]
10 20 ms 19 ms 23 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161]
11 24 ms 21 ms 20 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10]
12 22 ms 21 ms 21 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42]
13 24 ms 24 ms 22 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21]
14 48 ms 45 ms 49 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109]
15 39 ms 45 ms 38 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78]
16 55 ms 57 ms 57 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82]
17 59 ms 54 ms 55 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137]
18 57 ms 56 ms 54 ms bs-mia-gw2.customer.alter.net [65.208.86.130]
19 55 ms 54 ms 59 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19]
20 56 ms 55 ms 55 ms 65.83.237.9
21 53 ms 54 ms 61 ms 205.152.144.89
22 * * * Request timed out.
23 60 ms 61 ms 61 ms 208.62.23.150

Trace complete.

**PS I didn't see your last post before posted this Zardon, but I am using my command prompt to do this trace- have no idea if it still goes through IE6- I have never used another browser besides IE in my life- are there ones better? like maybe Mozilla or something? Do they have advantages in speed or anything? If so I will try it out. Are they free? Can you still have IE6 installed and working at the same time without effecting the other one?

I wonder if everyone else would get the same timeout on the same hop if thats anywhere near the DH server? Hmm, dunno.

*** ONe more interesting note that may help- if I am in part of the DH website that is going slow, (usually the submit button) sometimes if I hit the "stop" button on my browser, the page will pop right up, but maybee missing some info or only be a partial page or something.

I was on another website that did the SAME EXACT thing a few months ago and it turned out to be their addserver that was the problem, whatever that means.

Zardon · Mar 2, 2003, 03:40 PM

try Command Prompt and typing: ipconfig /flushdns

BWX · Mar 2, 2003, 03:40 PM

OK, will do that

Zardon · Mar 2, 2003, 03:41 PM

Quote:

Originally posted by BWX232

**PS I didn't see your last post before posted this Zardon, but I am using my command prompt to do this trace- have no idea if it still goes through IE6- I have never used another browser besides IE in my life- are there ones better? like maybe Mozilla or something? Do they have advantages in speed or anything? If so I will try it out. Are they free? Can you still have IE6 installed and working at the same time without effecting the other one?

try mozilla 1.3 and yes you can install it when you have IE6 installed it wont cause any problems, the reason im asking this is. I see some code errors atm in IE but not Mozilla. It probably wont make any difference, but its something id like you to try if you get time. to confirm either way.

and yes its free.

BWX · Mar 2, 2003, 03:51 PM

Oh man, forget that stuff I posted wth the tracert before, I was typing driverheaven.com not driverheaven.net-- here is the tracert for driverheaven.net - everything is fine and after the dns cach flush the driverheaven.com one still has the 22nd hop timing out.
Unless you are driverheaven.com too, I guess it doesn't matter.

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:************>ping driverheaven.net

Pinging driverheaven.net [216.127.74.135] with 32 bytes of data:

Reply from 216.127.74.135: bytes=32 time=48ms TTL=242
Reply from 216.127.74.135: bytes=32 time=49ms TTL=242
Reply from 216.127.74.135: bytes=32 time=56ms TTL=242
Reply from 216.127.74.135: bytes=32 time=53ms TTL=242

Ping statistics for 216.127.74.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 56ms, Average = 51ms

C:\***********>tracert 216.127.74.135

Tracing route to driverheaven.net [216.127.74.135]
over a maximum of 30 hops:

1 9 ms 9 ms 9 ms 10.0.196.1
2 9 ms 12 ms 12 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65]
3 22 ms 9 ms 9 ms 64.8.1.206
4 10 ms 10 ms 11 ms unk-426d0121.adelphiacom.net [66.109.1.33]
5 21 ms 22 ms 19 ms unk-426d00d9.adelphiacom.net [66.109.0.217]
6 20 ms 21 ms 21 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138]
7 19 ms 21 ms 25 ms g1-01-00-00.p0.chi75.adelphiacom.net [66.109.3.14]
8 34 ms 21 ms 22 ms pa2-atm0-1-aads-igr01.chi.twtelecom.net [206.220.243.116]
9 23 ms 22 ms 24 ms core-02-ge-0-3-0-0.chcg.twtelecom.net [168.215.53.193]
10 49 ms 55 ms 47 ms core-01-so-2-3-0-0.dlfw.twtelecom.net [168.215.53.46]
11 43 ms 43 ms 47 ms 66.192.246.69
12 47 ms 50 ms 51 ms dist-01-so-0-0-0-0.hsto.twtelecom.net [168.215.53.62]
13 48 ms 50 ms 48 ms hagg-01-ge-0-3-0.hsto.twtelecom.net [168.215.172.42]
14 58 ms 62 ms 52 ms 66.162.210.2
15 57 ms 53 ms 50 ms 207.218.245.38
16 51 ms 69 ms 49 ms driverheaven.net [216.127.74.135]

Trace complete.

Pinging driverheaven.com [208.62.23.150] with 32 bytes of data:

Reply from 208.62.23.150: bytes=32 time=57ms TTL=238
Reply from 208.62.23.150: bytes=32 time=61ms TTL=238
Reply from 208.62.23.150: bytes=32 time=59ms TTL=238
Reply from 208.62.23.150: bytes=32 time=57ms TTL=238

Ping statistics for 208.62.23.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 61ms, Average = 58ms

Tracing route to 208.62.23.150 over a maximum of 30 hops

1 16 ms 13 ms 23 ms 10.0.196.1
2 11 ms 7 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65]
3 9 ms 9 ms 9 ms 64.8.1.206
4 8 ms 12 ms 9 ms unk-426d0125.adelphiacom.net [66.109.1.37]
5 19 ms 21 ms 23 ms unk-426d00d9.adelphiacom.net [66.109.0.217]
6 31 ms 24 ms 24 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138]
7 25 ms 21 ms 23 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10]
8 21 ms 21 ms 21 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193]
9 22 ms 20 ms 22 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17]
10 20 ms 21 ms 24 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161]
11 21 ms 22 ms 21 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10]
12 22 ms 21 ms 19 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42]
13 22 ms 22 ms 22 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21]
14 46 ms 43 ms 44 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109]
15 40 ms 38 ms 40 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78]
16 61 ms 56 ms 60 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82]
17 56 ms 58 ms 58 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137]
18 56 ms 54 ms 55 ms bs-mia-gw2.customer.alter.net [65.208.86.130]
19 52 ms 68 ms 53 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19]
20 54 ms 51 ms 57 ms 65.83.237.9
21 53 ms 55 ms 53 ms 205.152.144.89
22 * * * Request timed out.
23 58 ms 61 ms 59 ms 208.62.23.150

Trace complete.

C:\*****

The first one is the corrct one the last one is the driverheaven.com tracert and ping which have a totally different IP address. Sorry about that.

Zardon · Mar 2, 2003, 03:55 PM

so driverheaven.net is ok for you?

BWX · Mar 2, 2003, 03:57 PM

Quote:

Originally posted by Zardon
try mozilla 1.3 and yes you can install it when you have IE6 installed it wont cause any problems, the reason im asking this is. I see some code errors atm in IE but not Mozilla. It probably wont make any difference, but its something id like you to try if you get time. to confirm either way.

and yes its free.

OK, I'll try Mozilla. Maybe all this started about the time I updated the latest so called "security patch" fpr IE6 on windows update. (last week sometime?) I'll have to see when I downloaded that update and if it was for IE or just a plain Windows update for windows itself. Only thing I can think of that was a change- And some other people are having minor problems too. Maybee they all downloaded that last windows update too.

BWX · Mar 2, 2003, 04:05 PM

Quote:

Originally posted by Zardon
so driverheaven.net is ok for you?

Well yes, as far as that (tracert) test goes, there are no timeouts like the driverheaven.com one as you see in my post above.

Driverheaven.com doesn't seem to be a real website though- it takes me to one of those 'domain names for sale' websites. I still have the weird slow down while posting even after the dns cach purge-- like now when i hit the submit reply button after posting. But the correct tracert has no timouts and the ping great for me at about 50 to 60 ms. Hmmm, strange.

If it was just me I would be sure it was on my end, but I was about to logof and saw this thread and thought I should check it out. Seems different fot different people?

ToshiroOC · Mar 2, 2003, 04:43 PM

I've been getting the exact same thing. Only when threads are loading, is there a problem. Main pages work fine, though searches take a while. Images take forever to load, as do the text... perhaps a couple minutes to open a few threads simultaneously... don't worry, you aren't the only one getting the slowdown.

Zardon · Mar 2, 2003, 04:46 PM

while I do understand there are people getting this problem, and im NOT ignoring them. im trying to figure out exactly what the problem is.

on my end the site is loading fine and I cant recreate any problems like this, and im in Ireland. server loads are almost non existant and the bandwidth is at 10% usage of the T3 line atm. so its not that either.

Im chatting with Andrew to see what can be done.

ToshiroOC · Mar 2, 2003, 05:03 PM

Everyone, please look to THIS THREAD HERE and continue the discussion there. This thread will be closed.

Feb 26, 2003, 05:23 PM	#1
CherryPopper DriverHeaven Lover Join Date: Dec 2002 Location: Toronto Posts: 132 Rep Power: 0	DriverHeaven Slow lately? Is it me or has the loading times for Driverheaven pages been much slower recently? I remember Zardon posting a while ago that loading times may increase since Driverheaven was hosting for Omega's new driver set, but i would expect that load to be a lot less now. __________________ Dell Precision 530 Workstation w Dual Xeon Processors @ 2 GHZ each 768 Megs PC 800 Rambus Ram ATI Radeon 9800 Pro 256 Meg DDRII Viewsonic VG191b Flatpanel Display Audigy 2 with 240 W THX Altec Lansing 5.1 Surround Speakers Fujitsu 36 Gig 10,000 rpm Ultra 160 SCSI HD Fujitsu 73 Gig 10,000 rpm Ultra 320 SCSI HD Windows XP Professional SP1 Build 2600

Feb 26, 2003, 05:53 PM	Thread Starter #3
CherryPopper DriverHeaven Lover Join Date: Dec 2002 Location: Toronto Posts: 132 Rep Power: 0	No problem.... thanks for the update Zardon. __________________ Dell Precision 530 Workstation w Dual Xeon Processors @ 2 GHZ each 768 Megs PC 800 Rambus Ram ATI Radeon 9800 Pro 256 Meg DDRII Viewsonic VG191b Flatpanel Display Audigy 2 with 240 W THX Altec Lansing 5.1 Surround Speakers Fujitsu 36 Gig 10,000 rpm Ultra 160 SCSI HD Fujitsu 73 Gig 10,000 rpm Ultra 320 SCSI HD Windows XP Professional SP1 Build 2600

Feb 26, 2003, 07:34 PM	#5
digitalwanderer Colour Commentator Join Date: May 2002 Location: Highland, IN USA Posts: 5,619 Rep Power: 0	It ain't the connection speed, but rather the time it takes the server to process the request and serve up the info...if'n that'll help you out any. __________________ WTF is up with the sigs?

Feb 27, 2003, 12:47 AM	#6
DriveEuro HardwareHeaven Extreme Member Join Date: Jul 2002 Location: Gurnee Illinois Posts: 4,677 Rep Power: 0	It's been noticeably slower to me too.... Eh who cares though.... Still quick enough. __________________ [color=orange]ASUS P4P800 Deluxe [color=black]-[/color] 2.4C --> 3300mhz [color=black]-[/color] Mushkin PC3200 at 220 5-2-2-2 (cpu limited) [color=black]-[/color] BBAti 9800Pro at 430/375 [/color] [color=black]3[/color][color=gray]D[/color]M[color=black]a[/color][color=gray]r[/color]k[color=yellow]01[/color] [color=black]3[/color][color=gray]D[/color]M[color=black]a[/color][color=gray]r[/color]k[color=yellow]03[/color] 16001200 12801024

Mar 2, 2003, 01:52 AM	#8
The_Neon_Cowboy HardwareHeaven Extreme Member Join Date: Dec 2002 Location: U.S.A. Posts: 16,009 Rep Power: 92 System Specs	Hey I have got a bain sTorm!!!! (scary I know) lets all run neotrace and post the info here (minus our IP's of couse)... then we can see if its a certin path the our data is takeing couseing the problems or the sever! couse its not on my end............... http://www.toast.net/performance/res...loadtime=1.051 __________________

Feb 26, 2003, 05:39 PM	#2
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	Well I certainly cant say im seeing it myself, but too many people are mentioning it for it to be one individuals machine or ISP causing problems. We have some forum problems atm, but I cant see how they are related to speed problems as server load is very low, so its not that which is causing the issues. im looking into it and im in talks with the adminstration staff. it may be a problem along some carrier line atm. sorry for any inconveniences.

Feb 26, 2003, 06:15 PM	#4
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	no I really am sorry its slow, im doing all I can, but I really dont know why it is for some people. the server location is texas, and im hearing from them there may be some outages over the coming days some maintenance on the time warner line. so lets leave it for until the weekend and see how it goes from there. server load is really low and our T3 line is more than capable of coping with our hits.

Feb 27, 2003, 01:26 AM	#7
fornicatarachnid Clanless Join Date: May 2002 Location: On the web, England UK Posts: 714 Rep Power: 0	mmmmm, interesting new sig Dig, what does it mean ?

Mar 2, 2003, 02:55 PM	#9
digitalwanderer Colour Commentator Join Date: May 2002 Location: Highland, IN USA Posts: 5,619 Rep Power: 0	It's getting slower....slowly but surely I'm noticing it take longer every day to serve up me pages. __________________ WTF is up with the sigs?

Mar 2, 2003, 03:22 PM	#11
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	For an experiment try an alternative browser. I wish I could reproduce this. I cant on any computer or connection ive tried. and I know for a fact server loads are almost zero.

Mar 2, 2003, 03:25 PM	#12
BWX unplugged Join Date: Nov 2002 Location: USNY Posts: 19,669 Rep Power: 110 System Specs	well, here it is again- I get the same timout on the same hop every single time. Maybee this is normal- I really have no idea. Maybe someone that knows can see something here. Microsoft(R) Windows DOS (C)Copyright Microsoft Corp 1990-2001. C:\*****\~***>ping driverheaven.com Pinging driverheaven.com [208.62.23.150] with 32 bytes of data: Reply from 208.62.23.150: bytes=32 time=56ms TTL=238 Reply from 208.62.23.150: bytes=32 time=60ms TTL=238 Reply from 208.62.23.150: bytes=32 time=58ms TTL=238 Reply from 208.62.23.150: bytes=32 time=56ms TTL=238 Ping statistics for 208.62.23.150: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 56ms, Maximum = 60ms, Average = 57ms C:\***~1\**~**>tracert 208.62.23.150 Tracing route to 208.62.23.150 over a maximum of 30 hops 1 10 ms 10 ms 8 ms 10.0.196.1 2 9 ms 9 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65] 3 7 ms 9 ms 9 ms 64.8.1.206 4 7 ms 9 ms 10 ms unk-426d0125.adelphiacom.net [66.109.1.37] 5 21 ms 19 ms 18 ms unk-426d00d9.adelphiacom.net [66.109.0.217] 6 22 ms 21 ms 19 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138] 7 22 ms 33 ms 20 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10] 8 23 ms 23 ms 23 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193] 9 20 ms 21 ms 19 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17] 10 24 ms 22 ms 22 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161] 11 23 ms 22 ms 23 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10] 12 21 ms 21 ms 22 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42] 13 22 ms 19 ms 24 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21] 14 46 ms 46 ms 47 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109] 15 38 ms 40 ms 38 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78] 16 72 ms 55 ms 56 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82] 17 82 ms 58 ms 56 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137] 18 55 ms 53 ms 54 ms bs-mia-gw2.customer.alter.net [65.208.86.130] 19 56 ms 54 ms 54 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19] 20 52 ms 57 ms 56 ms 65.83.237.9 21 57 ms 55 ms 55 ms 205.152.144.89 22 * * Request timed out. 23 70 ms 79 ms 58 ms 208.62.23.150 Trace complete. C:\******~1****>ping driverheaven.com Pinging driverheaven.com [208.62.23.150] with 32 bytes of data: Reply from 208.62.23.150: bytes=32 time=57ms TTL=238 Reply from 208.62.23.150: bytes=32 time=67ms TTL=238 Reply from 208.62.23.150: bytes=32 time=59ms TTL=238 Reply from 208.62.23.150: bytes=32 time=57ms TTL=238 Ping statistics for 208.62.23.150: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 57ms, Maximum = 67ms, Average = 60ms C:\***1\*~****>tracert 208.62.23.150 Tracing route to 208.62.23.150 over a maximum of 30 hops 1 9 ms 9 ms 10 ms 10.0.196.1 2 9 ms 8 ms 12 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65] 3 11 ms 12 ms 12 ms 64.8.1.206 4 7 ms 9 ms 8 ms unk-426d0125.adelphiacom.net [66.109.1.37] 5 26 ms 19 ms 24 ms unk-426d00d9.adelphiacom.net [66.109.0.217] 6 20 ms 22 ms 19 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138] 7 21 ms 24 ms 42 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10] 8 21 ms 20 ms 19 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193] 9 22 ms 19 ms 21 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17] 10 22 ms 24 ms 25 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161] 11 23 ms 23 ms 20 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10] 12 20 ms 24 ms 23 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42] 13 23 ms 25 ms 22 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21] 14 47 ms 44 ms 44 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109] 15 40 ms 38 ms 37 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78] 16 57 ms 54 ms 54 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82] 17 56 ms 55 ms 54 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137] 18 53 ms 54 ms 60 ms bs-mia-gw2.customer.alter.net [65.208.86.130] 19 55 ms 53 ms 56 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19] 20 56 ms 54 ms 54 ms 65.83.237.9 21 54 ms 54 ms 52 ms 205.152.144.89 22 * * Request timed out. 23 59 ms 73 ms 59 ms 208.62.23.150 Trace complete. C:\****~1\***8~***>tracert 208.62.23.150 Tracing route to 208.62.23.150 over a maximum of 30 hops 1 13 ms 7 ms 9 ms 10.0.196.1 2 6 ms 6 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65] 3 9 ms 9 ms 9 ms 64.8.1.206 4 9 ms 12 ms 9 ms unk-426d0125.adelphiacom.net [66.109.1.37] 5 20 ms 21 ms 19 ms unk-426d00d9.adelphiacom.net [66.109.0.217] 6 20 ms 24 ms 26 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138] 7 26 ms 35 ms 22 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10] 8 22 ms 25 ms 22 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193] 9 21 ms 22 ms 19 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17] 10 20 ms 19 ms 23 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161] 11 24 ms 21 ms 20 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10] 12 22 ms 21 ms 21 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42] 13 24 ms 24 ms 22 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21] 14 48 ms 45 ms 49 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109] 15 39 ms 45 ms 38 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78] 16 55 ms 57 ms 57 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82] 17 59 ms 54 ms 55 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137] 18 57 ms 56 ms 54 ms bs-mia-gw2.customer.alter.net [65.208.86.130] 19 55 ms 54 ms 59 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19] 20 56 ms 55 ms 55 ms 65.83.237.9 21 53 ms 54 ms 61 ms 205.152.144.89 22 * * Request timed out. 23 60 ms 61 ms 61 ms 208.62.23.150 Trace complete. PS I didn't see your last post before posted this Zardon, but I am using my command prompt to do this trace- have no idea if it still goes through IE6- I have never used another browser besides IE in my life- are there ones better? like maybe Mozilla or something? Do they have advantages in speed or anything? If so I will try it out. Are they free? Can you still have IE6 installed and working at the same time without effecting the other one? I wonder if everyone else would get the same timeout on the same hop if thats anywhere near the DH server? Hmm, dunno. * ONe more interesting note that may help- if I am in part of the DH website that is going slow, (usually the submit button) sometimes if I hit the "stop" button on my browser, the page will pop right up, but maybee missing some info or only be a partial page or something. I was on another website that did the SAME EXACT thing a few months ago and it turned out to be their addserver that was the problem, whatever that means. Last edited by BWX; Mar 2, 2003 at 03:39 PM.

Mar 2, 2003, 03:40 PM	#13
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	try Command Prompt and typing: ipconfig /flushdns

Mar 2, 2003, 03:51 PM	#16
BWX unplugged Join Date: Nov 2002 Location: USNY Posts: 19,669 Rep Power: 110 System Specs	Oh man, forget that stuff I posted wth the tracert before, I was typing driverheaven.com not driverheaven.net-- here is the tracert for driverheaven.net - everything is fine and after the dns cach flush the driverheaven.com one still has the 22nd hop timing out. Unless you are driverheaven.com too, I guess it doesn't matter. Microsoft(R) Windows DOS (C)Copyright Microsoft Corp 1990-2001. C:**********>ping driverheaven.net Pinging driverheaven.net [216.127.74.135] with 32 bytes of data: Reply from 216.127.74.135: bytes=32 time=48ms TTL=242 Reply from 216.127.74.135: bytes=32 time=49ms TTL=242 Reply from 216.127.74.135: bytes=32 time=56ms TTL=242 Reply from 216.127.74.135: bytes=32 time=53ms TTL=242 Ping statistics for 216.127.74.135: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 56ms, Average = 51ms C:\********>tracert 216.127.74.135 Tracing route to driverheaven.net [216.127.74.135] over a maximum of 30 hops: 1 9 ms 9 ms 9 ms 10.0.196.1 2 9 ms 12 ms 12 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65] 3 22 ms 9 ms 9 ms 64.8.1.206 4 10 ms 10 ms 11 ms unk-426d0121.adelphiacom.net [66.109.1.33] 5 21 ms 22 ms 19 ms unk-426d00d9.adelphiacom.net [66.109.0.217] 6 20 ms 21 ms 21 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138] 7 19 ms 21 ms 25 ms g1-01-00-00.p0.chi75.adelphiacom.net [66.109.3.14] 8 34 ms 21 ms 22 ms pa2-atm0-1-aads-igr01.chi.twtelecom.net [206.220.243.116] 9 23 ms 22 ms 24 ms core-02-ge-0-3-0-0.chcg.twtelecom.net [168.215.53.193] 10 49 ms 55 ms 47 ms core-01-so-2-3-0-0.dlfw.twtelecom.net [168.215.53.46] 11 43 ms 43 ms 47 ms 66.192.246.69 12 47 ms 50 ms 51 ms dist-01-so-0-0-0-0.hsto.twtelecom.net [168.215.53.62] 13 48 ms 50 ms 48 ms hagg-01-ge-0-3-0.hsto.twtelecom.net [168.215.172.42] 14 58 ms 62 ms 52 ms 66.162.210.2 15 57 ms 53 ms 50 ms 207.218.245.38 16 51 ms 69 ms 49 ms driverheaven.net [216.127.74.135] Trace complete. Pinging driverheaven.com [208.62.23.150] with 32 bytes of data: Reply from 208.62.23.150: bytes=32 time=57ms TTL=238 Reply from 208.62.23.150: bytes=32 time=61ms TTL=238 Reply from 208.62.23.150: bytes=32 time=59ms TTL=238 Reply from 208.62.23.150: bytes=32 time=57ms TTL=238 Ping statistics for 208.62.23.150: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 57ms, Maximum = 61ms, Average = 58ms Tracing route to 208.62.23.150 over a maximum of 30 hops 1 16 ms 13 ms 23 ms 10.0.196.1 2 11 ms 7 ms 9 ms g4-2.lasalle6509.buf.adelphia.net [68.65.14.65] 3 9 ms 9 ms 9 ms 64.8.1.206 4 8 ms 12 ms 9 ms unk-426d0125.adelphiacom.net [66.109.1.37] 5 19 ms 21 ms 23 ms unk-426d00d9.adelphiacom.net [66.109.0.217] 6 31 ms 24 ms 24 ms p3-00-00-00.r0.chi75.adelphiacom.net [66.109.0.138] 7 25 ms 21 ms 23 ms g1-00-00-00.p0.chi75.adelphiacom.net [66.109.3.10] 8 21 ms 21 ms 21 ms gigabitethernet1-0.ipcolo1.Chicago1.Level3.net [166.90.73.193] 9 22 ms 20 ms 22 ms gigabitethernet5-1.core1.Chicago1.Level3.net [209.244.8.17] 10 20 ms 21 ms 24 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161] 11 21 ms 22 ms 21 ms so-6-0-0.edge1.Chicago1.Level3.net [209.244.8.10] 12 22 ms 21 ms 19 ms POS1-2.BR1.CHI13.ALTER.NET [209.0.225.42] 13 22 ms 22 ms 22 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.73.21] 14 46 ms 43 ms 44 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET [152.63.67.109] 15 40 ms 38 ms 40 ms 0.so-3-1-0.TL2.ATL5.ALTER.NET [152.63.38.78] 16 61 ms 56 ms 60 ms 0.so-2-2-0.XL2.MIA4.ALTER.NET [152.63.81.82] 17 56 ms 58 ms 58 ms 0.so-7-0-0.GW8.MIA4.ALTER.NET [152.63.84.137] 18 56 ms 54 ms 55 ms bs-mia-gw2.customer.alter.net [65.208.86.130] 19 52 ms 68 ms 53 ms axr00mia-1-0-0.bellsouth.net [65.83.236.19] 20 54 ms 51 ms 57 ms 65.83.237.9 21 53 ms 55 ms 53 ms 205.152.144.89 22 * * Request timed out. 23 58 ms 61 ms 59 ms 208.62.23.150 Trace complete. C:\***** The first one is the corrct one the last one is the driverheaven.com tracert and ping which have a totally different IP address. Sorry about that. __________________

Mar 2, 2003, 03:55 PM	#17
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	so driverheaven.net is ok for you?

Mar 2, 2003, 04:43 PM	#20
ToshiroOC Unbiased. Join Date: Jun 2002 Posts: 4,812 Rep Power: 0	I've been getting the exact same thing. Only when threads are loading, is there a problem. Main pages work fine, though searches take a while. Images take forever to load, as do the text... perhaps a couple minutes to open a few threads simultaneously... don't worry, you aren't the only one getting the slowdown. __________________ [img][/img] [color=White]Peace be with you, Joe.[/color] Driverheaven Staff Member (Supermoderator)

Mar 2, 2003, 04:46 PM	#21
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	while I do understand there are people getting this problem, and im NOT ignoring them. im trying to figure out exactly what the problem is. on my end the site is loading fine and I cant recreate any problems like this, and im in Ireland. server loads are almost non existant and the bandwidth is at 10% usage of the T3 line atm. so its not that either. Im chatting with Andrew to see what can be done.

Mar 2, 2003, 05:03 PM	#22
ToshiroOC Unbiased. Join Date: Jun 2002 Posts: 4,812 Rep Power: 0	Everyone, please look to THIS THREAD HERE and continue the discussion there. This thread will be closed. __________________ [img][/img] [color=White]Peace be with you, Joe.[/color] Driverheaven Staff Member (Supermoderator)