MustangWorks.com : Ford Forums

MustangWorks.com : Ford Forums (http://forums.mustangworks.com/index.php)
-   Blue Oval Lounge (http://forums.mustangworks.com/forumdisplay.php?f=13)
-   -   Slow MustangWorks.... (http://forums.mustangworks.com/showthread.php?t=33107)

joe4speed 01-14-2003 07:55 PM

Slow MustangWorks....
 
Is it on my end or has it slowed down for everyone?? Just curious!

VeNuM 01-14-2003 09:05 PM

Seems just as quick for me (I'm on cable). Anybody else? ~Brian

mustangII460 01-14-2003 09:08 PM

The only problems I get, is getting into the msg forums. Everything else loads good. But I don't vist the other stuff much:(

ultraflo 01-14-2003 10:29 PM

I was having problems with this site a couple days ago... tonight it's working just fine. Dunno what the deal is. :confused:

PKRWUD 01-14-2003 10:48 PM

No problems tonight, but yeah, it was tough a couple days ago.

Crazy Horse GT 01-15-2003 01:01 AM

yeah working ok for me, got a couldnt find message mon night, but ok now. :) :D :D :D :D ;)

StangFlyer 01-15-2003 01:02 AM

The server is running fine, except for a problem I just fixed that was causing file attachments or avatar uploads to fail. This was due to something not being setup that should have been on the server (the forums were recently moved from one box to another). The server that runs the forums is dedicated to nothing but the forums.

Many things can effect the speed of the site... Like the number of users hitting the forums at any given time, although, it can handle quite a number of users at once. I haven't seen any type of server load issue since the Cobra abuse fiasco that should has seemed to adversely effected server performance. However, if a large number of people are transferring data across our sites as a whole (forums, media center, ad delivery, and everything else making up MW) and bandwidth usage is really high that might bog things a little bit. However, we have a large pipe to the Internet (a fractional T3 running at 2.5 Megabits) so I have never seen anything yet it didn't handle we've gotten hit with yet usage wise. At worst, a load of users might cause greater latency, but the bandwidth is there.

Outside our pipe and the hosting environment, there's your own ISP's network and the servers your traffic passes through to get here and back too. More often this is the cause of slowdowns, as during peek usage on the web many bottlenecks can occur slowing things down.

Crazy Horse GT 01-15-2003 01:08 AM

it's cool dan, your alway's on top of thing's, i guess it's a headache for you alot, thank's dan for your hard work. :) :D :D :D :cool:

joe4speed 01-15-2003 01:10 AM

hmmmm... yeah it might be me then...
here's my tracert to MW:
C:\Documents and Settings\Joe Lehman>tracert www.mustangworks.com

Tracing route to www.mustangworks.com [65.31.67.105]
over a maximum of 30 hops:

1 25 ms 25 ms 26 ms adsl-62-253-1.mia.bellsouth.net [208.62.253.1]
2 26 ms 27 ms 25 ms 209.215.49.97
3 26 ms 26 ms 25 ms 209.215.49.46
4 26 ms 25 ms 26 ms 65.83.237.8
5 43 ms 44 ms 43 ms 65.83.236.29
6 44 ms 43 ms 44 ms 65.83.236.36
7 55 ms 57 ms 57 ms so-2-0-0.gar2.dal1.Level3.net [67.72.4.1]
8 56 ms 57 ms 57 ms unknown.Level3.net [64.159.3.193]
9 89 ms 90 ms 91 ms so-0-0-0.mp1.Washington1.level3.net [64.159.0.13
8]
10 97 ms 97 ms 97 ms so-7-0-0.gar1.Washington1.Level3.net [64.159.1.1
90]
11 97 ms 99 ms 97 ms pop4-rtc-P5-0.atdn.net [66.185.140.153]
12 100 ms 100 ms 100 ms bb2-rtc-P15-0.atdn.net [66.185.140.146]
13 91 ms 90 ms 90 ms bb2-vie-P14-0.atdn.net [66.185.152.163]
14 118 ms 118 ms 119 ms bb2-chi-P6-0.atdn.net [66.185.152.214]
15 110 ms 111 ms 111 ms 66.185.148.67
16 118 ms 118 ms 117 ms 66.185.141.98
17 125 ms 126 ms 127 ms pos1-0.fmhlmi1-ubr1.twmi.rr.com [24.169.224.18]

18 120 ms 122 ms 120 ms pos1-0.fmhlmi1-ubr2.twmi.rr.com [24.169.224.14]

19 * * * Request timed out.
20 128 ms 130 ms 131 ms rrcs-central-65-31-67-105.biz.rr.com [65.31.67.1
05]

Trace complete.

and a ping:
C:\Documents and Settings\Joe Lehman>ping www.mustangworks.com

Pinging www.mustangworks.com [65.31.67.105] with 32 bytes of data:

Reply from 65.31.67.105: bytes=32 time=173ms TTL=103
Reply from 65.31.67.105: bytes=32 time=134ms TTL=103
Reply from 65.31.67.105: bytes=32 time=136ms TTL=103
Reply from 65.31.67.105: bytes=32 time=126ms TTL=103

Ping statistics for 65.31.67.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 173ms, Average = 142ms

C:\Documents and Settings\Joe Lehman>


yep, must be me... grrrrrrr
Thanks guys

Crazy Horse GT 01-15-2003 01:15 AM

yeah it's you joe, lol j/k.:p :D :D :D :D ;)

Topless In Texas 01-15-2003 02:07 AM

Me too...
 
I know I havent been on much this week. been busy w/ other stuff...and my computer has been a PIMFA all weekend and week!!!!! :mad:

BUT Joe, I noticed too, the times I was on , its slow too. :mad:

Every day that passes, I HATE My computer more. SRV..get ready, Im gonna hit you up for them parts in the next couple of months!!!!!!! Had a BRAINSTORM.....I betcha my BOSS will help me build it!!!! She can take a computer apart BLINDFOLDED! And I've been emailing her back and forth tonight about my sound card! ;) hehehhe........there might be light at the end of a LONG DARK TUNNEL!!!!! :rolleyes:
:rolleyes:TNT :rolleyes:

StangFlyer 01-15-2003 04:11 AM

Yeah, that ping average sucks. You have poor latency through the net right now. However, you were pinging the wrong server to test the FORUMS. You should have done a tracert and ping to "forums.mustangworks.com". It's a totally different server. :)

cyberstang5.0 01-15-2003 07:39 AM

It's been slow for me at work and at home. :rolleyes: :(

302 LX Eric 01-15-2003 08:32 AM

I haven't noticed any issues other than the fact that ever since we got DSL here at work everytime I jump on MW I have to re-enter my User name and Password. I have no idea why it does this as I've checked the little box on Internet Explorer that says 'please remember my password the next time I visit...'

Any ideas?

Sorry to hi-jack your thread, Joe.

E

cyberstang5.0 01-15-2003 12:36 PM

Make sure you Internet Exploder is setup to enable cookies.

jj_jonathon 01-15-2003 01:03 PM

Quote:

Originally posted by Dan McClain
Yeah, that ping average sucks. You have poor latency through the net right now. However, you were pinging the wrong server to test the FORUMS. You should have done a tracert and ping to "forums.mustangworks.com". It's a totally different server. :)
lol...but arent the boxes next to each other? :)

joe4speed 01-15-2003 01:44 PM

LOL I don't mind thread hijacking! :)



I get about the same when I ping there too:

Pinging forums.mustangworks.com [65.31.67.107] with 32 bytes of data:

Reply from 65.31.67.107: bytes=32 time=152ms TTL=104
Reply from 65.31.67.107: bytes=32 time=135ms TTL=104
Reply from 65.31.67.107: bytes=32 time=165ms TTL=104
Reply from 65.31.67.107: bytes=32 time=129ms TTL=104

Ping statistics for 65.31.67.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 129ms, Maximum = 165ms, Average = 145ms

C:\Documents and Settings\Joe Lehman>


oh well.... usually I'm real fast here, but lately it's slowed down, maybe they're having hardware issues at the CO.

Topless In Texas 01-16-2003 05:38 AM

wtf
 
I dont have a CLUE what the hell ya'll are talking about when your talking about PINGING....I think PING PONG....

Color me STUPID.....:rolleyes:
TNT:)

:mad:HATING MY COMPUTER AND 'THIS CLOSE' TO ENDING ITS LIFE......:mad:

induction 01-16-2003 02:34 PM

Re: wtf
 
Quote:

Originally posted by Topless In Texas
I dont have a CLUE what the hell ya'll are talking about when your talking about PINGING....I think PING PONG....

Color me STUPID.....:rolleyes:
TNT:)

:mad:HATING MY COMPUTER AND 'THIS CLOSE' TO ENDING ITS LIFE......:mad:

Hey TNT ...I think it has something to do with 'bad fuel' below 104 Octane or something:(

Topless In Texas 01-16-2003 04:44 PM

lol
 
I thought they were talking about computer ping, not engine ping...lol...god, I'm going back to bed! :D
TNT:cool:


All times are GMT -5. The time now is 10:05 AM.