From: Date: July 1 2009 9:35pm
Subject: RE: MySQL tuning
List-Archive: http://lists.mysql.com/mysql/218021
Message-Id: <30B3DF511CEC5C4DAE4D0D290504753413347028A2@AAA.pmgi.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

That's impossible to say with the limited information you've provided; howe=
ver, try this script for some basic tuning suggestions.  It should make sur=
e you're not doing anything crazy:

https://launchpad.net/mysql-tuning-primer

Regards,
Gavin Towey

-----Original Message-----
From: fa so [mailto:faka3o@stripped]
Sent: Tuesday, June 30, 2009 10:11 PM
To: mysql@stripped
Subject: MySQL tuning

Hi all,
I have a MySQL server with 1.7 GB of RAM, Some of the tables in my database=
 use MyISAM and others use InnoDB

Do you think the following mysql configurations are Ok? or should I change =
something?

innodb_buffer_pool_size =3D712M
innodb_additional_mem_pool_size =3D20M
innodb_log_buffer_size =3D8M
Current tmp_table_size  =3D 32 M
key_buffer_size   =3D 712M
max_allowed_packet  =3D 16M
thread_stack            =3D 128K
thread_cache_size       =3D 128
myisam-recover          =3D BACKUP
max_connections        =3D 1000
query_cache_limit       =3D 1M
query_cache_size        =3D 64M
expire_logs_days        =3D 10
max_binlog_size         =3D 100M

thank you





The information contained in this transmission may contain privileged and c=
onfidential information. It is intended only for the use of the person(s) n=
amed above. If you are not the intended recipient, you are hereby notified =
that any review, dissemination, distribution or duplication of this communi=
cation is strictly prohibited. If you are not the intended recipient, pleas=
e contact the sender by reply email and destroy all copies of the original =
message.