Quote:
Originally Posted by kermit2
If the server is just running Apache, I tend to find CPU to be the bottleneck - memory usage is modest, but PHP execution tends to be CPU hungry.
With a dedicated MySQL machine, you're hoping that as much of the database as possible will be cached in memory (faster than reading the data from disk), so memory tends to be the bottleneck. Of course MySQL can be CPU intensive too (eg when searching), but a lot of the time it isn't, and in those situations, having the data already cached in RAM can be a big performance boost.
If both Apache and MySQL are on the same box it's harder to know which is the bottleneck
|
ok, so the issue is bottleneck? would you suggest to keep it in a separate box ?