tag:blogger.com,1999:blog-4614960018934857975.post6774285676172756146..comments2023-11-27T09:32:36.643+00:00Comments on Mablomy: MySQL is so slow on Windows... Really?Unknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4614960018934857975.post-6676190591462610162017-07-05T10:36:50.891+01:002017-07-05T10:36:50.891+01:00Thank you for sharing. Your blog has given me that...Thank you for sharing. Your blog has given me that thing which I never expect to get from all over the websites. Nice post guys!<br /><br /><a href="http://www.papdan.com/" rel="nofollow">Melbourne Web Developer</a>seravina danniellahttps://www.blogger.com/profile/17416651554211077082noreply@blogger.comtag:blogger.com,1999:blog-4614960018934857975.post-15067024400398576072013-03-22T08:49:23.749+00:002013-03-22T08:49:23.749+00:00You are right. I will add that to the blog post. T...You are right. I will add that to the blog post. Thanks for spotting this.Mario Beckhttps://www.blogger.com/profile/04044394976329123982noreply@blogger.comtag:blogger.com,1999:blog-4614960018934857975.post-25172110304109252032013-03-22T08:34:36.117+00:002013-03-22T08:34:36.117+00:00Best performance will be with set innodb_flush_log...Best performance will be with set innodb_flush_log_at_trx_commit = 0<br />As stated in MySQL config:<br /><br />If set to 1, InnoDB will flush (fsync) the transaction logs to the<br />disk at each commit, which offers full ACID behavior. If you are<br />willing to compromise this safety, and you are running small<br />transactions, you may set this to 0 or 2 to reduce disk I/O to the<br />logs. Value 0 means that the log is only written to the log file and<br />the log file flushed to disk approximately once per second. Value 2<br />means the log is written to the log file at each commit, but the log<br />file is only flushed to disk approximately once per second.Vitaly Dyatlovhttps://www.blogger.com/profile/13707544514554521197noreply@blogger.com