On Tue, Nov 26, 2002 at 08:12:05PM +0100, Magnus Manske wrote:
Nick Hill wrote:
On Mon, 25 Nov 2002 19:21:57 -0500
"Poor, Edmund W" <Edmund.W.Poor(a)abc.com> wrote:
Your idea assumes that the "lag" problem
is due to overloading a single
machine, which plays double roles: database backeand and web server. So,
if we divide the work amoung 2 or more machines, you expect faster
throughput. Right?
My idea is not to divide the roles of web server and backend. It is to
divide the workload of the one server between many servers. This includes
search queries and other functionality.
<snip brave and expensive vision>
While the proposal of Nick will no doubt be the long-term future,
separating database server and webserver is both relatively cheap and
easy, and should increase performance. It is even recommended in either
the MySQL or the PHP online manual (or was it apache? Brain, where are
you?).
Even a smaller server might do, though I'm not sure wether to run apache
or MySQL on it. Probably the latter.
Hi,
do we have any numbers related to the CPU usage of the machine? Throwing
hardware at a performance issue is a solution that's chosen very often,
but it's
a) most of the time expensive
b) too often not the solution
In case of a high lag situation, which process is blocking the CPU? Is it
apache (that is: PHP) or mysql? How is the memory utilization? What is
the I/O rate?
Do we have this kind of data already available?
Best regards,
jens frank