Gaspar Bakos schrieb:
Hi,
Isn't the my-huge.cnf in the MySQL 5.0.22 distribution quite outdated?
It says "for systems with 512Mb RAM or more". Nowdays this is pretty
basic setup, and 'huge' is probably something in excess of 4Gb RAM.
I wonder if anyone has a recommendation for truly huge systems. For
example a dual CPU AMD opteron system with 4Gb (or 8Gb) RAM that is
fully devoted to serving the mysql daemon.
The config I have (see below) has been tuned to be optimal for creating
indexes on a large (100Gb+) single database table. It works fine
(although not satisfactory), but I worry that some parameters may have
an optimal value or range, and it does not make sense to increase them
like crazy.
Any opinions of the following : ?
[mysqld]
key_buffer_size=1024M
myisam_sort_buffer_size=256M
sort_buffer_size=256M
bulk_insert_buffer_size=64M
join_buffer_size=64M
max_connections=5
read_buffer_size=8M
read_rnd_buffer_size=8M
net_buffer_length=1M
max_allowed_packet=16M
# Cheers,
# Gaspar
Seriously.
You should get a hang on the mysql.cnf vars and values.
Guess we would answer to everyone on the list who wishes to optimize his
cnf.
"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?"
And "yes". You can tweak the shit out of the mysql.cnf files.
You have to test yourself on "your" system.
My only opinion would be to test it on a server which has the same
measures, so that the live project don't start acting weird.
And btw. the cnf files wrk with even bigger tables than you have.
Not "optimal" but "okay".
Every special server needs special handling. there is no "the one and
only you have to do it this way" way....
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]
