Posted by C. (http://symcbean.blogspot.com/) on 11/13/07 16:12

On 13 Nov, 09:47, "2401 members, SOME members can EVEN post"
<Paul_Me...@2cuk.co.uk> wrote:
>
> Ever suffer from too-much traffic ?
>
> Point is, if the traffic increases, then the server is slow.
>
> TOP command on a Linux/Unix/Fedora Apache/2.0.50 shows :
> - 50% of the CPU : for HTTPD process
> - 20% of the CPU : for Analog Process
> - 20% of the CPU : for MYSQLD Process
>
> The direct analysis would pretend that HTTPD is the problem. BUT may
> be HTTPD is waiting for MYSQLD answer.
> We have problem to analyse the sources of the lack of performance.
>
> 1) Idea ONE was to split sub.domains within other servers with
> independant databases merged and consolidated into a single one using
> exchange of tables.
>
> 2) Idea TWO was to have MYSQL hosted on one server and sub.domains
> split over different servers.
>
> SERVER1 : MYSQL
> SERVER2 : oaks.bobby.com
> SERVER3 : liveoaks.bobby.com
> SERVER4 : bobby.com
>
> We know ebay is ebay.com and these administrators might split over
> servers depending on variables that our team does not manage.
>
> 3) We tried to go with Idea TWO and we are facing a problem.
>
> Creating a user on SERVER1
> Name : bobbob
> Data Privilege : SELECT
> INSERT
> UPDATE
> DELETE
> FILE
>
> Information related to connections
> Server : % (all servers)
>
> FLUSH PRIVILEGES ;
>
> Then, on SERVER2 :
> <?
>
> $host = "207.36.16.15";
> $user = "bobbob";
> $pass = "bobbob";
> $bdd = "adv_database";
> ?>
>
> It does not work : Cannot access the database on SERVER1 from SERVER2.
> Even, we tried to add specfic provileges to bobbob.
>
> Many Thanks for any operational answer from your knowledge and
> background experience.
>
> .Bob

Cutting away all the crud from your post - you don't seem able to
connect to mysql from a remote host. This is a well documented and
very FAQ - try google.

Apache and PHP are quite goos at not using up CPU when waiting for
resources - making the DB go faster isn't going to reduce the amount
of CPU time used by Apache (actually it will increase v. slightly if
you move the DB off the localhost).

Moving sub-domains onto specific servers is probably the dumbest way
to solve this problem - once you've googled how to connect to a remote
mysql database, lookup 'Round Robin DNS' and 'PHP session handler
MySQL'; you want to split the load across multiple, identically
configured webservers then you get the benefit of fault tolerance too.
How you replicate the files is up to you.

C.

[Back to original message]