Comments on: How to calculate a good InnoDB log file size - recap

By: shlomi

shlomi — Fri, 02 Dec 2011 06:11:24 +0000

@George,
I suppose I would have to live with it
Seriously, Percona Server supports > 4G worth of transaction log files.
Perhaps you can tune you app so as to produce less transactions; i.e. group more statements into transactions (may not reduce overall size, but will help out with flushes), work out smarter queries, take out logging from the database...

By: George

George — Thu, 01 Dec 2011 15:40:02 +0000

Thanks for the snippet. Very handy.

What would you do if you got this result though? Seems a 36G log file might be a bad thing to have.

+------------------------------------------+---------------------------------------------+
| estimated_innodb_os_log_written_per_hour | estimated_innodb_os_log_written_per_hour_mb |
+------------------------------------------+---------------------------------------------+
| 38325872640 | 36550.4MB |
+------------------------------------------+---------------------------------------------+

By: shlomi

shlomi — Wed, 05 Jan 2011 05:24:10 +0000

My best guess is that you're NOT using 5.1. Perhaps just the 5.1 client.

Try:
mysql> SELECT VERSION();

By: sonny

sonny — Tue, 04 Jan 2011 21:13:52 +0000

GLOBAL_STATUS table is not exist in INFORMATION_SCHEMA database. using 5.1. Am I mising something...

Pls help.

By: shlomi

shlomi — Wed, 21 Oct 2009 04:19:54 +0000

Hi Arjen,

Thanks. I have an awk 'pager' for that, but it's really ugly...

By: Arjen Lentz

Arjen Lentz — Wed, 21 Oct 2009 01:18:30 +0000

Very cool Shlomi!
Would be great to do this in 5.0 also, but that might be a shell thing since you can't get status within a query.