The site is very slow...

[TheGoose]

Typical LAMP applications, MySQL server is the weakest link. You can turn on the slow query log and find out what sorts of SELECTs are occurring and how long they take after a predetermined threshold, in seconds.

Can it cause users to experience slow downs? It most certainly will. In the right, um, undesirable conditions.

Amiga.org is interesting case because it does almost as many writes as it does reads. Well, reads will always be higher of course (Franko is on vacation I understand). And some of the most common requests can be cached and should be (like the front page loading).

Personally, only have had few searches get hung up, but try again and they succeed. That's a MySQL issue, not your connection, not PHP.

Of course there are other considerations as to the setup, hosting, hardware and a hundred other factors, so my recommendation as professional web developer is to reload the page.

:roflmao:

[TheGoose]

TheGoose  
That's how it is for me a little slow or I click again and off it goes :confused:  but not enuf to annoy me though ,using win 7 64 -fire fox .

Other thing that may be causing odd periodical slowdowns (for visitors) are:

cron jobs - you can look that up yourself.

scheduled database backups (usually running late at night, but where is late night you might ask - timezone), depending on how big the databases is; Amiga.org I would be frightened to know.

So the site is alive, doing its own things at times, like pooping. And you just walking in on it doing that, and it slams the door shut, I'm pooping!

Does that help?

[TheGoose]

It has nothing to do with Ads, we blame Windows.

Oh no! Amiga.org is WAMP not LAMP.

Or maybe WIMP , like I run ! :lol:

[TheGoose]

@smerf

You laugh now but we are upgrading Amiga.org to a TRS 80 web server in the near future.

Always thinking ahead, that's what I like about this place. :lol:

[TheGoose]

I've identified what may be the cause of most of the 500 errors. It's an old bug, originally reported by Piru:

http://www.amiga.org/forums/project.php?issueid=62

This is the fault of a 3rd party module that the site is which uses a vBulletin "hook" (injects some code) that thanks to a lack of sanity checking fails fatally on evaluation, causing the 500 error.

Disabling the module is not an option for now, I've added a quick work-around (injects the required sanity checks into the hook - lol, injecting the injected code...) that should hopefully mitigate the issue until such time that the actual module itself can be updated/fixed.

Karlos has set the sanity injectors 10! Close your eyes!  :lol:

[TheGoose]

if (strpos($hook, 'shareads')!==false) {
   $hook = str_replace(
      '$output = $vbam->',
      'if (is_object($vbam)) $output = $vbam->',
      $hook
   );


Eeewww, so you are actually running a string replace on the actual vbulletin code that is suspect, why not just fix it at the source then patching it at run time?

So the replacement part here does the extra step of seeing if the $vbam is in fact an object first, if so, let it go and set it to be the $output

duct tape, if it works....

[TheGoose]

Did you read the post?

Maybe a little overlap there.  :smack:

[TheGoose]

Me too, been at home, now work, no problems.

Looks like some chmod issues above...

[TheGoose]

How many of you are following links in from the "top stats" thing at the bottom of the home page?

never touch the stuff.

[TheGoose]

Just posting to kick down a thread I don't like appearing on my Amiga forum community...

move along...

[TheGoose]

I'm really puzzled by this mystery. And I still do not have any trouble reaching or loading the site from home(Time Warner) or work (University).

Still, other are having some real consistent trouble.

Hmmm, makes me think about NameServers/DNS and who is handling it? Has it always been the same? Some of these descriptions sound like the name could not be resolved.