Comments on: Choosing proper innodb_log_file_size http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/ Everything about MySQL Performance Fri, 05 Dec 2008 08:42:04 +0000 http://wordpress.org/?v=2.5.1 By: How to calculate a good InnoDB log file size | MySQL Performance Blog http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-388366 How to calculate a good InnoDB log file size | MySQL Performance Blog Fri, 21 Nov 2008 14:52:45 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-388366 [...] write a post a while ago about choosing a good InnoDB log file size.  Not to pick on Peter, but the post actually kind of talks about a lot of things and then doesn't [...] [...] write a post a while ago about choosing a good InnoDB log file size.  Not to pick on Peter, but the post actually kind of talks about a lot of things and then doesn’t [...]

]]> By: peter http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-149190 peter Tue, 24 Jul 2007 21:37:50 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-149190 It is combined size which is limited It is combined size which is limited

]]> By: Seth http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-149171 Seth Tue, 24 Jul 2007 20:17:47 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-149171 I am a little confused by this line: Note at this poing 4GB is maximum combined size allowed for innodb log files My question is what is combined to get this 4GB maximum? Is it innodb_log_files_in_group * innodb_log_file_size or is there another part of equation I am missing? I am a little confused by this line:
Note at this poing 4GB is maximum combined size allowed for innodb log files

My question is what is combined to get this 4GB maximum? Is it innodb_log_files_in_group * innodb_log_file_size or is there another part of equation I am missing?

]]> By: 选择合适的innodb_log_file_size at 周俭 Blog http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-4676 选择合适的innodb_log_file_size at 周俭 Blog Mon, 02 Oct 2006 00:15:33 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-4676 [...] 原文作者： Peter Zaitsev原文来源： http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/译者：叶金荣（Email:），转载请注明译者和出处，并且不能用于商业用途，违者必究。 [...] [...] 原文作者： Peter Zaitsev原文来源： http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/译者：叶金荣（Email:），转载请注明译者和出处，并且不能用于商业用途，违者必究。 [...]

]]> By: peter http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-1572 peter Tue, 08 Aug 2006 13:51:49 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-1572 Hi you're right. My typo. It should be "Where not commited" of course. Hi you’re right. My typo. It should be “Where not commited” of course.

]]> By: Yuan WANG http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-1571 Yuan WANG Tue, 08 Aug 2006 13:45:34 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-1571 I'm a litter confused with the following sentence. "Innodb will need to roll back certain transactions which were commited, but changes from which already made it to the database.". Why rollback the transactions which were commited? If the a transaction is commited, according to the ACID property of transaction, it should not be rolled back. I’m a litter confused with the following sentence. “Innodb will need to roll back certain transactions which were commited, but changes from which already made it to the database.”. Why rollback the transactions which were commited? If the a transaction is commited, according to the ACID property of transaction, it should not be rolled back.

]]> By: MySQL Performance Blog » MySQL Crash Recovery http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-1302 MySQL Performance Blog » MySQL Crash Recovery Sun, 30 Jul 2006 18:09:30 +0000 http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/#comment-1302 [...] Innodb Recovery - Unless you have some hardware problems (99%) or found new Innodb bug (1%) Innodb recovery should be automatic and bring your database to consistent state. Depending on innodb_flush_lot_at_trx_commit setting you may lose few last committed transactions but it is it. It is Performance of this process which may cause the problems. As I already wrote innodb_log_file_size and innodb_buffer_pool_size affect recovery time significantly as well as your workload. I should also mention if you have innodb_file_per_table=1 your recovery speed will depend on number of Innodb tables you have, as well as many other operations, so beware. [...] [...] Innodb Recovery - Unless you have some hardware problems (99%) or found new Innodb bug (1%) Innodb recovery should be automatic and bring your database to consistent state. Depending on innodb_flush_lot_at_trx_commit setting you may lose few last committed transactions but it is it. It is Performance of this process which may cause the problems. As I already wrote innodb_log_file_size and innodb_buffer_pool_size affect recovery time significantly as well as your workload. I should also mention if you have innodb_file_per_table=1 your recovery speed will depend on number of Innodb tables you have, as well as many other operations, so beware. [...]

]]>