Jump to content

Benefits Of Having MySQL On A Remote Server?


Recommended Posts

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.

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.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.