Well for myself I will better like to have the 2 computer design, 1 for
httpd and 1 for mysql, it's alway's better that way the few nano that
you lose in transit are way better then a server that do both stuff. Now
the problem (that eat a lot of time is php and mysql, doh!). So you have
optimise that, is mysql will be mostly for read or write data what kind
of %, if you need more read or more accurate read then write I suggest
you to have a lot of heap table (in memory table, put them read only and
get them to regenerate at every x times), copy of the mainly used data
in your application, with a lot of ram that will speed-up the main
thing. Then an other thing is to take big table and put them in smaller
table, way faster for writing/reading (hum, I don't quite remember if
mysql is row locking or table locking during write?).
Then they other best stuff is to make your dynamic page (.php) and to
make them static page (.html) this way you will get way faster viewing
page, you don't have they overload of neither php, nor mysql processing.
khttpd anyone?
Anyway, you could do a lot of stuff, load-balacing, an other server for
just your image, ...
If you want more, you should go at http://www.slashdot.org/ and do a
little search on that subjectthey had a few good article on that on the
last few month, year,...
Jay Paulson wrote:
>
> Hello everyone-
>
> I need some expert advice so I turn you to all! :)
>
> I'm am currently in the process of making 7 web sites using PHP and MySQL
> backend. I'm porjecting that all of these sites combined will get a million
> plus hits a month easy when it's all said and done. What I'm wanting to do
> is to put the database on it's own machine and put the sites on a different
> machine to reduce the cpu load. However, I'm not 100% sure this is the best
> option. I know there are a ton of variables to consider with this situation
> and I'm trying to figure out the best way to go so I don't have to redo it
> again.
>
> I'm thinking with the traffic these servers are going to incur if they are
> on one computer then I should probably have a dual CPU with a gig of ram or
> more and two hard drives.. Once CPU for serving up the pages and once CPU to
> run the db. Also, one HD for the db and one HD for the pages in trying to
> get the most performace out of one machine.
>
> Some of the dedicated options that people have thrown to me are in the range
> of a 450 CPU with 512 Ram and 30GB drive. I don't think that with so many
> pages being served that this system will handle it.
>
> Any suggestions?
>
> Thanks,
> jay
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
Francis Fillion, BAA SI
Broadcasting live from his linux box.
And the maintainer of http://www.windplanet.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
