I am just an old country boy and dont have a clue what this means but i changed the 350/4 barrell/with cam,popup pistons,hi-rise edelbrock manifold,dual holley 850 double pumpers Isky points and plugs and this thing is still slow! Hope this helps:bandit: FLY SAFE T.C.Try this..
When you are experencing slow page loads right click the page and select view source. This is the raw html that the server is sending to your browser. If you scan through the text you will see that the page has loaded but it is yet to be displayed. I think that it is the javascript loading the ads.
57ms from your tracert is good.
Tracing route to jetcareers.com [84.40.28.95]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.185.1
2 <1 ms <1 ms <1 ms vl164.pttid01.or.integraonline.net [64.122.164.2
]
3 <1 ms <1 ms <1 ms v50.pttid01.integra.net [209.63.115.226]
4 2 ms 2 ms 2 ms fe9-3.bv18d51.integra.net [209.63.115.229]
5 3 ms 3 ms 3 ms ge2-24--3.cr01.ptleorte.integra.net [209.63.115.
157]
6 7 ms 7 ms 7 ms tg13-1.cr01.sttlwatw.integra.net [209.63.114.97]
7 8 ms 7 ms 7 ms tg1-1.br01.sttlwawb.integra.net [209.63.114.134]
8 7 ms 7 ms 7 ms ge-6-10-232.car2.Seattle1.Level3.net [4.79.104.1
17]
9 7 ms 17 ms 17 ms ae-32-56.ebr2.Seattle1.Level3.net [4.68.105.190]
10 62 ms 55 ms 54 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
11 67 ms 55 ms 55 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
12 57 ms 72 ms 58 ms ae-2.ebr1.Dallas1.Level3.net [4.69.132.106]
13 91 ms 81 ms 85 ms ae-7-7.car2.Tampa1.Level3.net [4.69.133.41]
14 82 ms 82 ms 81 ms ae-24-24.car4.Tampa1.Level3.net [4.69.133.66]
15 86 ms 88 ms 89 ms HOSTWAY-COR.car4.Tampa1.Level3.net [4.71.2.14]
16 87 ms 88 ms 83 ms e1-2.dr2.as30217.net [84.40.24.106]
17 82 ms 83 ms 86 ms lma3075.tam.us.siteprotect.com [84.40.28.95]
Trace complete.
C:\Documents and Settings\>pathping jetcareers.com
Tracing route to jetcareers.com [84.40.28.95]
over a maximum of 30 hops:
0 ICO-xxxxxxx-xxxx 192.168.185.109]
1 192.168.185.1
2 vl164.pttid01.or.integraonline.net [64.122.164.2]
3 v50.pttid01.integra.net [209.63.115.226]
4 fe9-3.bv18d51.integra.net [209.63.115.229]
5 ge2-24--3.cr01.ptleorte.integra.net [209.63.115.157]
6 tg13-1.cr01.sttlwatw.integra.net [209.63.114.97]
7 tg1-1.br01.sttlwawb.integra.net [209.63.114.134]
8 ge-6-10-232.car2.Seattle1.Level3.net [4.79.104.117]
9 ae-32-56.ebr2.Seattle1.Level3.net [4.68.105.190]
10 ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
11 ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
12 ae-2.ebr1.Dallas1.Level3.net [4.69.132.106]
13 ae-7-7.car2.Tampa1.Level3.net [4.69.133.41]
14 ae-24-24.car4.Tampa1.Level3.net [4.69.133.66]
15 HOSTWAY-COR.car4.Tampa1.Level3.net [4.71.2.14]
16 e1-2.dr2.as30217.net [84.40.24.106]
17 lma3075.tam.us.siteprotect.com [84.40.28.95]
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ICO-JPULFER.ads.integratelecom.com
[192.168.185.109]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.185.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% vl164.pttid01.or.integraonline.net
[64.122.164.2]
0/ 100 = 0% |
3 0ms 0/ 100 = 0% 0/ 100 = 0% v50.pttid01.integra.net [209.63.11
5.226]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% fe9-3.bv18d51.integra.net [209.63.
115.229]
0/ 100 = 0% |
5 4ms 1/ 100 = 1% 1/ 100 = 1% ge2-24--3.cr01.ptleorte.integra.ne
t [209.63.115.157]
0/ 100 = 0% |
6 11ms 0/ 100 = 0% 0/ 100 = 0% tg13-1.cr01.sttlwatw.integra.net [
209.63.114.97]
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% tg1-1.br01.sttlwawb.integra.net [2
09.63.114.134]
0/ 100 = 0% |
8 13ms 0/ 100 = 0% 0/ 100 = 0% ge-6-10-232.car2.Seattle1.Level3.n
et [4.79.104.117]
0/ 100 = 0% |
9 12ms 0/ 100 = 0% 0/ 100 = 0% ae-32-56.ebr2.Seattle1.Level3.net
[4.68.105.190]
0/ 100 = 0% |
10 60ms 0/ 100 = 0% 0/ 100 = 0% ae-2.ebr2.Denver1.Level3.net [4.69
.132.54]
0/ 100 = 0% |
11 60ms 0/ 100 = 0% 0/ 100 = 0% ae-1-100.ebr1.Denver1.Level3.net [
4.69.132.37]
0/ 100 = 0% |
12 59ms 0/ 100 = 0% 0/ 100 = 0% ae-2.ebr1.Dallas1.Level3.net [4.69
.132.106]
0/ 100 = 0% |
13 88ms 0/ 100 = 0% 0/ 100 = 0% ae-7-7.car2.Tampa1.Level3.net [4.6
9.133.41]
0/ 100 = 0% |
14 91ms 0/ 100 = 0% 0/ 100 = 0% ae-24-24.car4.Tampa1.Level3.net [4
.69.133.66]
0/ 100 = 0% |
15 80ms 0/ 100 = 0% 0/ 100 = 0% HOSTWAY-COR.car4.Tampa1.Level3.net
[4.71.2.14]
0/ 100 = 0% |
16 81ms 0/ 100 = 0% 0/ 100 = 0% e1-2.dr2.as30217.net [84.40.24.106
]
0/ 100 = 0% |
17 81ms 0/ 100 = 0% 0/ 100 = 0% lma3075.tam.us.siteprotect.com [84
.40.28.95]
Trace complete.
Tracing route to jetcareers.com [84.40.28.95]
over a maximum of 30 hops:
1 1 ms <10 ms <10 ms 10.6.18.1
2 1 ms 1 ms 1 ms 207.191.46.94
3 42 ms 16 ms 7 ms 207.191.46.93
4 134 ms 104 ms 87 ms peer-01-so-1-0-0-0.dlfw.twtelecom.net[66.192.246.53]
5 35 ms 17 ms 12 ms 64.132.69.42
6 40 ms 39 ms 39 ms mai-b1-pos0-0-0.telia.net [213.248.80.38]
7 283 ms 81 ms 179 ms hostway-115911-mai-b1.c.telia.net[213.248.81.10]
8 453 ms 336 ms 205 ms 66.113.197.41
9 209 ms 163 ms 106 ms 84.40.24.50
10 95 ms 67 ms 90 ms e1-2.dr2.as30217.net [84.40.24.106]
11 146 ms 146 ms 67 ms jetcareers.com [84.40.28.95]
Trace complete.
Pinging jetcareers.com [84.40.28.95] with 32 bytes of data:
Reply from 84.40.28.95: bytes=32 time=102ms TTL=37
Reply from 84.40.28.95: bytes=32 time=114ms TTL=37
Reply from 84.40.28.95: bytes=32 time=213ms TTL=37
Reply from 84.40.28.95: bytes=32 time=99ms TTL=37
Ping statistics for 84.40.28.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 213ms, Average = 132ms
Tracing route to jetcareers.com [84.40.28.95]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.6.18.1
2 1 ms 1 ms 1 ms 207.191.46.94
3 8 ms 13 ms 10 ms 207.191.46.93
4 81 ms 30 ms 12 ms peer-01-so-1-0-0-0.dlfw.twtelecom.net[66.192.246.53]
5 9 ms 23 ms 10 ms 64.132.69.42
6 147 ms 136 ms 102 ms mai-b1-pos0-0-0.telia.net [213.248.80.38]
7 139 ms 186 ms 116 ms hostway-115911-mai-b1.c.telia.net[213.248.81.10]
8 144 ms 93 ms 68 ms 66.113.197.41
9 193 ms 65 ms 68 ms 84.40.24.50
10 81 ms 77 ms 83 ms e1-2.dr2.as30217.net [84.40.24.106]
11 88 ms 68 ms 67 ms jetcareers.com [84.40.28.95]
Trace complete.
Pinging jetcareers.com [84.40.28.95] with 32 bytes of data:
Reply from 84.40.28.95: bytes=32 time=66ms TTL=37
Reply from 84.40.28.95: bytes=32 time=67ms TTL=37
Reply from 84.40.28.95: bytes=32 time=66ms TTL=37
Reply from 84.40.28.95: bytes=32 time=66ms TTL=37
Ping statistics for 84.40.28.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 67ms, Average = 66ms
Tracing route to jetcareers.com [84.40.28.95]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 10 ms 10 ms 9 ms ppp-69-221-239-254.dsl.klmzmi.ameritech.net[69.221.239.254]
4 11 ms 10 ms 11 ms dist2-vlan60.klmzmi.ameritech.net[67.36.55.243]
5 11 ms 10 ms 10 ms bb1-g1-0.klmzmi.ameritech.net [67.36.55.99]
6 14 ms 15 ms 15 ms 151.164.94.41
7 14 ms 15 ms 14 ms Te-3-2.Chicago1.Level3.net [4.68.110.197]
8 15 ms 16 ms 18 ms ae-32-54.ebr2.Chicago1.Level3.net[4.68.101.126]
9 42 ms 38 ms 51 ms ae-3.ebr2.Atlanta2.Level3.net [4.69.132.74]
10 56 ms 56 ms 57 ms ae-5-5.car1.Tampa1.Level3.net [4.69.133.49]
11 56 ms 58 ms 57 ms ae-14-14.car4.Tampa1.Level3.net[4.69.133.58]
12 56 ms 56 ms 57 ms HOSTWAY-COR.car4.Tampa1.Level3.net[4.71.2.14]
13 57 ms 57 ms 57 ms e1-2.dr2.as30217.net [84.40.24.106]
14 57 ms 57 ms 56 ms lma3075.tam.us.siteprotect.com [84.40.28.95]
Trace complete.
Pinging jetcareers.com [84.40.28.95] with 32 bytes of data:
Reply from 84.40.28.95: bytes=32 time=58ms TTL=48
Reply from 84.40.28.95: bytes=32 time=57ms TTL=48
Reply from 84.40.28.95: bytes=32 time=57ms TTL=48
Reply from 84.40.28.95: bytes=32 time=57ms TTL=48
Ping statistics for 84.40.28.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 58ms, Average = 57ms
but anyways, it might come down to having to prune the forum and getting rid of a few years worth of threads. I kinda wonder what would happen, if anything, if we did that... would it even be worth it?
yeah, i've noticed some pretty good slowness both yesterday and today...
so far, hostway has offered the suggestions of buying a 2nd dedicated server saying that mysql is taking up all the processing power....interesting considering we probably don't match up to some of the greatest commercial websites and their bandwidth/processing...i know we need to find a solution and soon...so i'll be bugging the webmaster once new years is past. It needs to become his number 1 task.
but anyways, it might come down to having to prune the forum and getting rid of a few years worth of threads. I kinda wonder what would happen, if anything, if we did that... would it even be worth it?
but anyways, it might come down to having to prune the forum and getting rid of a few years worth of threads. I kinda wonder what would happen, if anything, if we did that... would it even be worth it?