From owner-freebsd-questions Thu Mar 30 3:10:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A1A4F37B72A for ; Thu, 30 Mar 2000 03:10:51 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12acqS-0005Hs-00; Thu, 30 Mar 2000 13:10:36 +0200 From: Sheldon Hearn To: "Sean Heber" Cc: questions@FreeBSD.ORG Subject: Re: Flooded in hits! Suggestions? In-reply-to: Your message of "Wed, 29 Mar 2000 15:36:20 CST." <000d01bf99c6$d38a6520$f97338d1@central.edu> Date: Thu, 30 Mar 2000 13:10:36 +0200 Message-ID: <20327.954414636@axl.ops.uunet.co.za> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Mar 2000 15:36:20 CST, "Sean Heber" wrote: > It seems mySQL just can't keep up and the queries are taking too long > to complete. So, not only does that make the site slow, but very > quickly Apache reaches its maximum client limit and so things get > REALLY slow (since the queries are slow and you have to wait for an > open connection and all those backed up connections that are active > are slowing mysql down even more, etc..). Your immediate problem, then, is how to prevent SQL saturation. This is most easily accomplished in the short term by limiting the number of Apache client connections to some small number that SQL _can_ handle. Once you have your server back off its knees, you can start worrying about proxies and SQL fine-tuning. But first things first. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message