Hi Merlin,
It depends where most of the current load is being generated.
If the majority of the load is coming from the processing of the website
you would be better having the database and web server on different
boxes - this will reduce the load on both servers and compensate for the
lag you will be unable to avoid when communicating over a network (not
to mention the SSL overheads).
If, however, the majority of the load is generated by the database then
you wouldn't affect the processing speed of the new box much by putting
the web server on it, and so would see a greater speed increase from
connecting to the database through the unix socket.
Jonathon Wardman
http://www.fubra.com/ - http://uk3.php.net/
Merlin wrote:
Hi there,
I do have a LAMP app that currently does run on a 1GB i686 Prozessor.
The system is getting slower since traffic is raising. So I ordered
another dedicated root server with an Opteron 4GB Raid System.
I intended to run the second box as a pure DB Server and do the PHP
and Weberserving stuff do the old machine.
Here is the problem:
After the system is setup, I noticed that I have to configure mysql
with SSL, do some other restrictions and that latency might become a
problem since
I do not really know where the boxes are located within my provider
(same one).
Which version do you think will be the faster and/or smarter way to go:
1. Put all on the new box and let it handle mysql via socket without
SSL between web/db
2. Put on seperate boxes, go over SSL (MySQL4.1.22), without static
compile option (does not work with SSL), connected through internet.
Option one would also be 100 Euro cheaper per month. Server load is
currently between 1.5 and sometimes 5.
Thank you for any help on this triky question.
Best regards,
merlin
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
