Hi, I really doubt putting PHP files (or any site files) on a RAM disk will make any performance difference; and certainly not 30-50%. When the files/scripts are accessed, they are cached by the OS. So, in effect, they are automatically put in a sort of "RAM disk." The disk is definitely NOT accessed each time the file is requested.
This doesn't matter anyway (for the PHP), since he said he's using PHP Accelerator, which caches the compiled code in shared memory. And this does save the slight overhead of file reading calls (and the very costly and slow PHP parser/compiler :-)) -- except stat() or whatever to check the mtime. Matt ----- Original Message ----- From: "mos" Sent: Wednesday, October 22, 2003 1:44 PM Subject: Re: Mysql Performance Question > At 12:32 PM 10/21/2003, you wrote: > >Thanks a lot guys. > > > >Haydies: > > > > >Just out of wondering, are you using PHP and if so do you use > >mysql_pconnect > > >rather then mysql_connect because that would really speed things up..... > > > >I tired pconnect before but it didn't help but using up all the available > >memory. It speeds up things until the disks started swapping, which happened > >in a few hours after the server was up and running. > > > >Gabriel: > > Gabriel, > You can also create a small RAM disk and put all of the PHP > scripts and images on that drive. It will speed things up by 30%-50%. And > you're right about "pconnect". It doesn't speed things up. There are PHP > debuggers available that have a profiler that will show you which of your > PHP functions are slow. It could be only 1 or two functions that need > optimizing. Also I insist on putting a LIMIT 100 or LIMIT 25 on my web > queries to reduce the number of rows returned. This should speed things up > quite a bit. > > Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
