> We are currently building a webfarm to replace our all in one box solution. We are experiencing problems when we get linked to a site like the drudgereport and we are seeing 1000's of hits a minute. Both apache and mysql start chocking and we get dropped because we cant deliver content. I am trying to understand what is the best way to redeploy our Mysql. > > I am thinking of two possible designs, if feasible. The clients are read only there is no inserting or deleting. The database is updated nightly from a single source.
The first thing I would suggest to to run your apache and mysql on a different box, also you said your clients are read only and your DB would be updated nightly from a single source, so keeping that in mind figure 2 seems to be a better soution, use MYISAM as your tables as you only need reads. > In Fig 1 I am thinking that each server runs both apache and the mysql engine and the database files will live on the SAN. Is this possible? can multiple engines talk to one database file on the SAN? No I dont think this is possible in Mysql, even if it is it might not be feasible. >We are going to deploy HP proliant ml 585 with quad AMD 2.2 Opterons with 12 gigs of ram. With that in mind how many mysql sessions can I be able to support? refer to http://kjalleda.googlepages.com/maxconnbymysql to calculate this value.... I would also advice you to have some kind of Failover or High Availabilty in place for Mysql. Kishore Jalleda http://kjalleda.googlepages.com/projects On 4/8/06, Elias <[EMAIL PROTECTED]> wrote: > We are currently building a webfarm to replace our all in one box solution. We are experiencing problems when we get linked to a site like the drudgereport and we are seeing 1000's of hits a minute. Both apache and mysql start chocking and we get dropped because we cant deliver content. I am trying to understand what is the best way to redeploy our Mysql. > > I am thinking of two possible designs, if feasible. The clients are read only there is no inserting or deleting. The database is updated nightly from a single source. > > > Fig 1 > _____________ > | http | > | Mysql | > |_____________| > _____________ > | http | > _______ _____________ | Mysql | _____________ > | PIX | | Load Balance | |_____________| | | > | | ---| |------ _____________ -------| SAN | > |_______| |____________ | | http | |____________ | > | Mysql | > |_____________| > _____________ > | http | > | Mysql | > |_____________| > > In Fig 1 I am thinking that each server runs both apache and the mysql engine and the database files will live on the SAN. Is this possible? can multiple engines talk to one database file on the SAN? > > Fig 2 > _____________ > | http | > | | > |_____________| > _____________ > | http | > _______ _____________ | | _____________ ______________ > | PIX | | Load Balance | |_____________| | | | | > | | ---| |------ _____________ -------| Mysql |---- | SAN | > |_______| |____________ | | http | |____________ | |_____________ | > | | > |_____________| > > > In fig 2 the 3 apache servers would query the single myql server. > > All the data and scripts would live on the SAN. Or would it be better and faster to have the data live on the mysql server and the scripts live on the SAN? > > We are going to deploy HP proliant ml 585 with quad AMD 2.2 Opterons with 12 gigs of ram. With that in mind how many mysql sessions can I be able to support? > > > Any suggestions, comments, thoughts of clarity would be greatly appreciated. > > Regards to all, > Michael > > > >
