On 6/12/06, Gaspar Bakos <[EMAIL PROTECTED]> wrote:
---------- Forwarded message ----------
Date: Mon, 12 Jun 2006 11:39:11 -0400 (EDT)
From: Gaspar Bakos
To: Barry <[EMAIL PROTECTED]>
Subject: Re: my-huge.cnf quite outdated
Hello, Barry,
RE:
> Guess we would answer to everyone on the list who wishes to optimize his
> cnf.
That was unpolite, since the OP asked for simple guidelines and
pointed out that default example config files were outdated, not
begging for advice and/or help.
I don't guess, and don't even expect that you answer to everyone.
> "Oh, i have add super X RAMs with latencies of blah blah. Please i
> think my cnf is outdated can somone help me?" Or: "Oh, i have added a
> HD with 2times more rounds per/m can you update my cnf PLZ?"
These are not what I asked, they are pretty negative exaggarations.
The OP got a point here, if you don't wanna help, don't bother answer...
> And "yes". You can tweak the shit out of the mysql.cnf files.
> You have to test yourself on "your" system.
This is what I am doing, and in the meantime, looking for experience,
and also sharing mine.
I've had a big time looking for configs over the net and manuals,
ended search with this:
http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html
Quite handy if used with:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html
And in your particular case, with:
http://dev.mysql.com/doc/refman/5.0/en/memory-use.html
and
http://dev.mysql.com/doc/refman/5.0/en/disk-issues.html
Got a very fast setup here, but my machine is not as powerful as
yours, so, won't post it...
> And btw. the cnf files wrk with even bigger tables than you have.
> Not "optimal" but "okay".
How big?
Get a "default" set is something hard to do. You say machines with
more than 1GB of RAM are "standard", but where I live, that's not
true. For big companies with HUGE databases and servers, MySQL
provides specific help with optimization (pay contracts), and the
default files served as a base for me for the last 5 years or so.
> Every special server needs special handling. there is no "the one and
> only you have to do it this way" way....
OK, so why is there a my-{small,large,huge}.cnf ?
They are guidelines for typical systems and applications.
But they are quite outdated, as typical systems changed.
Simple guidelines for complete newbies to start with MySQL and learn
their way easily... They are not for typical systems, they are
specially SAFE and minimally optimized configs so your server won't
crash, but still use some of the resources of the machine. Keep in
mind that for me a HUGE server has 2GB of RAM and tables of 80GB, but
not for you, and I would not want a config file to simply crash
because its expecting 4GB of RAM... Neither a disk outbreak because
its caching my small tables (compared to yours) completely using swap
and spinning up my disks to a overheat...
All in all: I was looking for _typical_ configs for 4GB+ machines and
100Gb+ tables.
There are not such configs, sorry, but you gotta test your configs
because I don't think anyone would give you a config set that may
crash/overload/put in risk your server. Simply grab a set of features
and play in a test database. There are some "stress tests" for mysql
over the web...
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
