We finally split our huge logging aspect of an application to its own system,
and we changed the table type from InnoDB to MyIsam. This is a logging table,
1 log writer, many, many selects from customer care reps looking up the last
500 or so records. These are logs of timed events, so they
I was running a table in InnoDB, and the table had about 6 indexes, none
of which seemed to be affected when I ran mysqlbinlog against the tables
in order to apply bin-logs from production against a test system. I was
manage to process upwards of 2300 queries per second by throwing about
1.8 GB
I have a curious issue here, maybe someone can help.
I have a single process that inserts data into tables that contain purely
logging information. This table is then searched by our Care department to
troubleshoot issues. I am looking for the best way to store this data, and the
structure
of the table by the logwriter, hence the need to truncate the
table. But while it is truncating, the table hung, hence the need for InnoDB.
Thomas.
-Original Message-
From: Jeremy Cole [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 18, 2005 2:28 PM
To: Thomas Lekai
Cc: mysql
: Tuesday, January 18, 2005 3:30 PM
To: Thomas Lekai
Cc: mysql@lists.mysql.com
Subject: Re: Logging Data: Should I use MyIsam or InnoDB?
Hi Thomas,
Thanks, this is what I was originally thinking of, but how I am
getting rid of the data in log_view_today? OR, are you saying that
log_view_today
