[ale] Building a Linux/Mysql Database server.

[The Don Lachlan]

On Tue, May 24, 2011 at 12:26:08AM -0400, Atlanta Geek wrote:
> I wasnt very clear.  I actually need to define the specs for a mysql
> database server.
> Our current server is a Quad Core ~2GHz 4 Gig 2 15k drive (no raid)
> configuration. And It seems to be I/O bound on a lot of operations.
> The database  as is goes to around 45 Gig.
> This new server needs to be able to handle our same database structure
> with about 600 Gig of data.  There's a lot of writing and reading of
> data.
> Any suggestions on hardware.  Can Mysql deal with 32 Gig or is this a
> waste of resources because its not enough to cache.  Would we be
> better off looking at SSDs .
> Any guidance would be appreciated.

If you're referring to RAM, MySQL can handle 32GB of RAM just fine.

Disk I/O is a common bottleneck, especially in databases. SSD is likely
overkill; SCSI or SAS (Serial-Attached-SCSI) in RAID10 should be fine but I
would avoid standard SATA.

I'm guessing (hoping!) that expanding your DB from 45G to 600G will also
include some tuning of the database and application. As such, performance
will change and your current bottleneck(s) may be resolved.

Without more information about your applications and what the current
performance is or what the _expected_ performance will be, it's impossible
to be specific. Is your application focused on reads from the DB? Writes?
50/50%? How much data? How quickly? Are constantly you re-reading the same
data? How many CPU cycles for a standard query? Can't answer your questions
without more information. Give us some numbers, man!

-L (But what I said about RAID10 is gospel.)


> 
> Date: Mon, 23 May 2011 10:19:01 -0400
> From: Chuck Payne <terrorpup at gmail.com>
> Subject: Re: [ale] Building a Linux/Mysql Database server.
> To: Atlanta Linux Enthusiasts <ale at ale.org>
> Message-ID: <BANLkTi=+wn=Dr5qfkDCb6gXZT+32ksuouQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On Mon, May 23, 2011 at 9:57 AM, Dennis Ruzeski <denniruz at gmail.com> wrote:
> > The setup of the database would essentially be the same as if it were
> > local except you would need to allow access for the web user to access
> > the database from the web server(s). Example-
> >
> > grant select,insert,update on database.* to `user`@`10.10.10.10`
> > identified by 'password';
> >
> > Substitute in your user name, web server IP, password, and required privileges.
> >
> > Make sure to cycle the server or run "flush privileges;" for the
> > changes to take effect.
> >
> >
> >
> > On Mon, May 23, 2011 at 9:40 AM, Atlanta Geek <atlantageek at gmail.com> wrote:
> >> All,
> >> I need to take a single server product that we sell and make it
> >> multi-server. However I am having trouble finding some guidelines on
> >> how to build the database server. Does anyone have any links or
> >> suggestions.
> >>
> >> Can someone recommend a mysql mailing list as well.
> >>
> >> --
> >> http://www.atlantageek.com
> >> _______________________________________________
> >> Ale mailing list
> >> Ale at ale.org
> >> http://mail.ale.org/mailman/listinfo/ale
> >> See JOBS, ANNOUNCE and SCHOOLS lists at
> >> http://mail.ale.org/mailman/listinfo
> >>
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://mail.ale.org/mailman/listinfo/ale
> > See JOBS, ANNOUNCE and SCHOOLS lists at
> > http://mail.ale.org/mailman/listinfo
> >
> 
> Are you trying to set up master/slave mysql server? Just set up mysql
> server? What are you tryign to do, here are a few links.
> 
> http://www.howtoforge.com/how-to-set-up-mysql-database-replication-with-ssl-encryption-on-debian-lenny
> 
> http://dev.mysql.com/tech-resources/articles/mysql_intro.html
> 
> http://www.devshed.com/c/a/MySQL/Beginning-MySQL-Tutorial/
> 
> 
> 
> -- 
> http://www.atlantageek.com
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo