Pardon me, looks like i haven't answered the original question after all. Need coffee.
Here is another attempt. Have you considered mysql replication? this is an easy way of building both a fail safe system as well as to balance the load. the drawback is that you need to pay for an extra server.
best regards. raditha
Raditha Dissanayake wrote:
pconnect vs connect: Isn't it what the apache project calls the 'stampeding herd' problem?
original question: Nicole one of the simplest, cheapest and best solutions is to put your log files on a separate hard disk. you will be amazed by the result. You would ofcouse get even better results if you switched to RAID. (assuming of course that you haven't done so already)
Curt Zirzow wrote:
* Thus wrote Chris Shiflett ([EMAIL PROTECTED]):
--- Nicole <[EMAIL PROTECTED]> wrote:
Originally, I used pconnect for a while. Then I learned that with
high traffic site, that's not the best idea.
Where did you learn this? I disagree with that notion.
This may be debatable, which is better? php searching through a pool of 1000 connections for a free one or the overhead of opening a new resource to the database each request.
Curt
-- Raditha Dissanayake. ------------------------------------------------------------------------ http://www.radinks.com/sftp/ | http://www.raditha/megaupload/ Lean and mean Secure FTP applet with | Mega Upload - PHP file uploader Graphical User Inteface. Just 150 KB | with progress bar.
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
