From: Tom Horstmann (tomutome.de)
Date: Thu Sep 04 2008 - 16:25:24 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Addendum..
Please also try increasing your innodb_log_file_size to a much higher value
if you
have lots of writes/transactions. Maybe 250MB is a good first try.
You need to delete/move the InnoDB logs before restart.

Not sure about this, but please also set innodb_log_buffer_size. Try
something
between 16-32MB if you have many transactions.

TomH

-----Original Message-----
From: Tom Horstmann [mailto:tomutome.de]
Sent: Thursday, September 04, 2008 11:15 PM
To: 'Josh Miller'
Cc: mysqllists.mysql.com
Subject: RE: innodb/myisam performance issues

> The rows in this table are accessed concurrently as any activity on the
> site is recorded/added/updated to this table. We have several others
> which serve similar purposes, (sessions, totaltraffic, etc...).

Is the performance lag occurring with read-only queries and updates/inserts
to the InnoDB table?
Is the table mostly read or more written?

You could set innodb_flush_log_at_trx_commit=2 if you may loose the latest
InnoDB
writes in case of a MySQL crash. It should give you much less IO for writes
on your
InnoDB tables.
Please see http://dev.mysql.com/doc/refman/4.1/en/innodb-parameters.html for
a
detailed description.

Please also read about innodb_flush_method at this site and possibly try
other settings.

TomH

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=tomutome.de

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]