Benefits Of Having MySQL On A Remote Server?

[Zero3X]

Say I have a script on server A which connects to a database and performs (for example) 10 queries a minute. If this database was stored on server B would server A benefit? Would the RAM or bandwidth use of server A be reduced?

[The Little Guy]

Apache is on server A, and MySQL is on server B, they now have the ability to take a higher load.

 

if MySQL is bogging down server B, it won't affect Apache on server A, unless you have a script trying to talk to MySQL on server B.

 

Lets say you are running a intensive script that is using 90+% CPU server B will/may become very slow and almost unresponsive. If this happens and Apache is on the same server, it will have a harder time trying to answer incoming requests. By splitting the two up, Apache can respond almost instantly in the same situation. But if your web script that is running from Apache (server A) needs to talk to MySQL (server B) it will slow down.

[ManiacDan]

The only reason do split into two servers is to alleviate load problems (or for some very obscure security reasons).  If you don't have any load problems (which you shouldn't at 1 query every 6 seconds) then you don't need to split them.  Splitting unnecessarily will actually hurt, since you'll be increasing your page load times waiting for DB connections across the network.

[fenway]

Depends how 'remote' it is.