Re: my-huge.cnf quite outdated (fwd)
Gaspar Bakos schrieb:
-- 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.
I don't guess, and don't even expect that you answer to everyone.
Well if everyone would start posting his cnf. You would end up
confused. That's what i pointed out with it.
Sometimes it is good to guess.
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.
Well yes you did. Well they are negative but in the end you will face
this. There are no typical 8GB, SATA II 2TB filesystem RAID clustered,
with high connection network card configs out there that would run
smooothly on your system. It's just as it is.
You have to do it by yourself.
You would be lucky as hell finding somone with the same hardware config
as you have.
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.
Experience is only gained by doing.
I did configured Server which had half a terrabyte of data and that was
no fun at all.
When you get further in this you will see that at the end you only have
two ways of accomplishing it.
Reading every manual you get about the cnf and get a hang on what every
variable do or get a customer contract and let somone configure it.
And btw. the cnf files wrk with even bigger tables than you have.
Not optimal but okay.
How big?
i tested them with 350 GB files on a 4GB RAM 500GB SATA raid1 system.
And was stable.
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.
Because those cnf do give a push in a way you want to go but when you
want optimized configs you have to specialise it depending on the server.
That's what i said. nothing more or less
All in all: I was looking for _typical_ configs for 4GB+ machines and
100Gb+ tables.
Now guess this time. There isn't something like that.
Barry
--
Smileys rule (cX.x)C --o(^_^o)
Dance for me! ^(^_^)o (o^_^)o o(^_^)^ o(^_^o)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: my-huge.cnf quite outdated (fwd)
-- 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.
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.
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.
And btw. the cnf files wrk with even bigger tables than you have.
Not optimal but okay.
How big?
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.
All in all: I was looking for _typical_ configs for 4GB+ machines and
100Gb+ tables.
G
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: my-huge.cnf quite outdated (fwd)
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]
Re: my-huge.cnf quite outdated (fwd)
Hi, Daniel, RE: 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 [...] Thanks for the links, I will check them again. I read most of those that are available on the web. 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 I see. To re-iterate the question, I think the missing info is 1. the useful domain of system parameters. For example, read_buffer 64M does not help at all because of other limitations. (the default is 8K if I recall correctly). 2. the relation between the parameters, as they have a complicated relation. It is usually quite meaningless to increase/decrease a sinle parameter without changing others. So later on I will probably ask or share experience on the reasonable range on specific parameters. 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... Good idea to google for stress tests. Cheers Gaspar -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
