EN2 very much slower

[Michael Morris]

At least I'm not alone in experiencing a slow problem with ENW2.

At first I thought I was logging on at peak hours, but it seems every hours are peak hours on ENW2. It couldn't be my connection since I upgraded to DSL. Ironic, it was only when I have dial-up it was fast ... ENW1 that is.

How about we go back to ENW1?

Not possible. And how soon do you forget these problems where present on the old codebase as well.

 

[Nifft]

And how soon do you forget these problems where present on the old codebase as well.

QFT. IMHO v2's worst is still better than how v1 was just before the upgrade.

I wish I knew about MySQL specifically.

Cheers, -- N

 

[Obryn]

EN2 seems much faster, overall, than EN1 was - when I'm able to connect, at least.

At other times, everything times out. It's either fast or nonexistent. Hardly anything in between.

I remember EN1 being even worse, though, so it's still an improvement.

-O

 

[wedgeski]

Not possible. And how soon do you forget these problems where present on the old codebase as well.

To be fair, the only time I can remember ENW behaving like this was right before the last major server drive, when access speeds slowed to a crawl at any time the US was awake. Now, the site veers between superb responsiveness and constant time-outs every five minutes. Something is very wrong.

 

[cougent]

I have seen both the very slow and the very fast, just hours apart from each other. I am not sure what the prime time hours are for the site, but being in Central US time zone I only seem to have real problems in the 6AM to 9AM timeframe. Also during the 2AM to 5AM window the site is very responsive.

I agree with Nift that ENW2 at its worst is still NOWHERE near ENW1 at its worst. Perhaps that is because I now get Network Timeouts after about 45 seconds and have to reload whereas with ENW1 I remember times when it just sat there "loading" for up to 10 minutes and never did. [I would hit another tab and come back later to find it still loading] I greatly prefer the error message over the endless loop of the past.

 

[stonegod]

Is it a mySQL problem? I thought the latest culprit was the httpd settings (if I understand this thread).

Of course, with our main sysadmin having to look for a job while trying to nail this down, I understand any delays in getting it fixed. Its fast enough for me most times (and I can wait it out in others).

 

[Michael Morris]

I'm beginning to think the box is rooted again. The pattern is invariant - 10-15 minutes of quick response then major lag. Hidden cron job perhaps? I've no idea how to look for or fix the problem if it is intrusion. I've tried different settings each night for the last week folks. I'm sorry, but this problem is beyond me to fix.

 

[sjmiller]

I am glad to see I am not the only one experiencing slowness and network time out issues. I thought maybe it was me. I started to really notice them a couple weeks ago when I switched to Firefox 3. I thought maybe it was an issue with Firefox. Connecting to ENWorld, loading threads, even loading the reply to thread screen is often incredibly slow. Makes me wish I know current programming languages.

 

[drothgery]

Makes me wish I know current programming languages.

I do, but the wrong ones. If the site was on the Microsoft stack (ASP.NET/SQL Server), then I might be able to help out. Though the site I built and maintain gets a lot less traffic than ENWorld (even if it does bring in more money).

 

[Filcher]

Laggy lag lag?

It might be just me, but during the day trying to get into ENworld is like trying to read a new comic posted on Order of the Stick.

(I knew it was bad when I started going over to read the Wizards board.)

Is this just me getting the "no server on the other side" response, or is ENworld's popularity killing it?