New server a little slow for me...
 

Page loads or new threads are taking 8-10 seconds to come up. I'm connecting to the internet at 6033Kbps btw. It actually seems slower than before for whatever reason.

Greg

UPDATE: When I submitted this message, it took like 15-20 seconds to post.

Seems slower for me, too...

Same here too...........a lot slower.

I'm good.

I have to agree.

I actaully have fewer hops to the new server, and its working well from NC. The slowest one is 103ms.

Noticeably slower for me too.

Actually it was slow earlier this morning but it's back to normal now. The site is being revamped so it's one of the expected glitches.

Happy surfing now.!!

Much Slower
 

Currently 19:46 UTC here in the UK and the site is massively slower than it used to be. Takes between 8-10 seconds to load a page. 30 seconds just to log in.

Line tests show less that 8kBps from the site on a 2M/Bit line (232kBps approx)

Needs some more money in the meter methinks.

Server Load Averages0.12 0.07 0.07 | 72 Users Online (37 members and 35 guests)

its the DNS routing, and not the server. the server load is minimal -- less than 1/10th what it used to be.

remember, the DNS settings were changed and those can take up to 72 hours to resolve over the internet. the server itself is rocking fast. the connection from your end to the server may not be 'optimized' as the DNSs are not all pointed to the right server.

a.gtld-servers.net [192.5.6.30]ns1.cedgecons.com. ns2.cedgecons.com. 35msc.gtld-servers.net [192.26.92.30]ns1.cedgecons.com. ns2.cedgecons.com. 35msg.gtld-servers.net [192.42.93.30]ns1.cedgecons.com. ns2.cedgecons.com. 135msh.gtld-servers.net [192.54.112.30]ns1.cedgecons.com. ns2.cedgecons.com. 135msi.gtld-servers.net [192.43.172.30]ns1.cedgecons.com. ns2.cedgecons.com. 135msd.gtld-servers.net [192.31.80.30]ns1.cedgecons.com. ns2.cedgecons.com. 135msl.gtld-servers.net [192.41.162.30]ns1.cedgecons.com. ns2.cedgecons.com. 135msf.gtld-servers.net [192.35.51.30]ns1.cedgecons.com. ns2.cedgecons.com. 135msk.gtld-servers.net [192.52.178.30]ns1.cedgecons.com. ns2.cedgecons.com. 136mse.gtld-servers.net [192.12.94.30]ns1.cedgecons.com. ns2.cedgecons.com. 136msj.gtld-servers.net [192.48.79.30]ns1.cedgecons.com. ns2.cedgecons.com. 244msb.gtld-servers.net [192.33.14.30]ns1.cedgecons.com. ns2.cedgecons.com. 378msm.gtld-servers.net [192.55.83.30]ns1.cedgecons.com. ns2.cedgecons.com. 378ms

the problem is the #s to the right... the first two are what i am getting...

give it a little time..

greg- posting here is instantaneous....

I just hit "quote" to reply to this message, and it took about 12 seconds, yikes. I'm sure you're right. Let's give it a while. Here's an FYI... UPDATE: It took about 25 seconds to post this message.

Time to look up xoutpost.com A record
Generated by www.DNSstuff.com at 20:00:25 GMT on 18 Jan 2006.
Searching for xoutpost.com A record at i.root-servers.net Got referral to K.GTLD-SERVERS.NET. [took 183 ms]
Searching for xoutpost.com A record at K.GTLD-SERVERS.NET. Got referral to ns1.cedgecons.com. [took 89 ms]
Searching for xoutpost.com A record at ns1.cedgecons.com. Timed out. Trying again.
Searching for xoutpost.com A record at ns1.cedgecons.com. Reports an answer.

Record is:


Domain Type Class TTL Answer xoutpost.com. A IN 14400 64.62.200.216 xoutpost.com. NS IN 86400 ns1.cedgecons.com. xoutpost.com. NS IN 86400 ns2.cedgecons.com. ns1.cedgecons.com. A IN 14400 64.62.200.216 ns2.cedgecons.com. A IN 14400 64.62.200.210

Looking up at ns1.cedgecons.com.... Timed out.
Looking up at ns2.cedgecons.com.... Timed out.


Average of all 2 nameservers: 1246ms (plus 1684ms overhead).

Score: F

Took off 15 points for a nameserver timeout at ns1.cedgecons.com (causes lengthy delays and extra packets).
Took off 15 points for a nameserver timeout at ns2.cedgecons.com (causes lengthy delays and extra packets).
Took off 25 points for >700ms average response time.

Note: The 1684ms overhead is the time it takes to get your NS records from the parent servers, and indicates a worst-case scenario (normally, the resolving DNS server would have the common parent server entries cached, and would know the parent server(s) that were responding most quickly). The best times since the last time this web server was last restarted are: 1ms average response, plus 6ms overhead. Note that these times are from a server located in the United States; if most of the people using your DNS are outside of the United States, your actual results may be better than what is shown here. A rating of 'B' or higher is generally good (this tool is very picky!). This tool is designed to make an educated guess about speed, and to point out potential factors that may reduce the DNS speed, and it is not perfect.

DrDrex: posting here is "quick" but, not as fast as it was.
The long situ is page loadups, (non-posting). Almost timing out...

No complaint, just an observation. The orig page load up, via my Faves, takes a Long time...page flips, cruising around also is slow. Dunno what a DNS, etc. is, but maybe it just needs time.

I tried the dump cache thing that Gresch had mentioned but I either did it incorrectly or, in my situ, that "dump/clear" thing did not/does not work for me...and, dunno if that would help.

NEway, good job on the changeover. It should speed up, it seems.

This Site is a FookinDrug, lol!
BR,md

Edit: now, my post(s) are lightning fast.

any better now?

No, sorry. We'll be patient, it takes time I know.

according to the registrar, up to 72 hours.... :(

i'm hitting the server directly even faster now... <20 msecs

DrDrex: Mine is flying, now!

Posting, lookups, page flips, backup on browser, etc....it is freaking humming!
BR,md

:iagree: I'm at a hotel in the Chicago area and it's screaming fast for me. For those that are still seeing slow response, give it a little bit of time for the DSN settings to propogage through the internet properly and all should be well.

Yep, doing good now. Problem solved, I think. Thanks guys, you are the best :thumbup: :thumbup: :thumbup: :thumbup:

No problem here

Perhaps it's just us on the other side of the Atlantic then.

I even checked it on our work system and it made no difference. different network, different location.

How long before the 72 hours is up?

I booted up my Powerbook 1400C (Made in 1993) and we are running X5World wirelessly. What a hoot to see that old laptop doing it's thing.

It's retribution for the freaking Stamp Act, etc...

:jk: , sorta.;)

BR,md

[email protected]