Comments on: MySQL 4.1 Binary Log name change http://www.sitepoint.com/blogs/2005/06/30/mysql-41-binary-log-name-change/ Sun, 07 Sep 2008 18:56:53 +0000 http://wordpress.org/?v=2.5 By: danut http://www.sitepoint.com/blogs/2005/06/30/mysql-41-binary-log-name-change/#comment-5233 danut Wed, 31 Dec 1969 19:00:00 +0000 #comment-5233 <p>Congratulations about your jump to MySQL 4.1<br /> Good job.</p> Congratulations about your jump to MySQL 4.1
Good job.

]]> By: dtra http://www.sitepoint.com/blogs/2005/06/30/mysql-41-binary-log-name-change/#comment-5234 dtra Wed, 31 Dec 1969 19:00:00 +0000 #comment-5234 <p>did you go to mysql 4.1.12<br /> we recently went from 4.1.7 to 4.1.12<br /> and found a huge performance increase<br /> uses threading instead of pre-fork (or something, that's what our sysadmin said)</p> did you go to mysql 4.1.12
we recently went from 4.1.7 to 4.1.12
and found a huge performance increase
uses threading instead of pre-fork (or something, that’s what our sysadmin said)

]]> By: Steffen http://www.sitepoint.com/blogs/2005/06/30/mysql-41-binary-log-name-change/#comment-5235 Steffen Wed, 31 Dec 1969 19:00:00 +0000 #comment-5235 <p>You are sure that your admin was not talking about Apache? :-)</p> You are sure that your admin was not talking about Apache? :-)

]]> By: Etnu http://www.sitepoint.com/blogs/2005/06/30/mysql-41-binary-log-name-change/#comment-5236 Etnu Wed, 31 Dec 1969 19:00:00 +0000 #comment-5236 <p>You won't see any significant improvement jumping from mysql 4.0 to 4.1 UNLESS you also upgrade to php5, and begin rewriting your code to use prepared queries.</p> <p>Some people might see slight increases with full text indexes, InnoDB tables, and the general relative performance of importing data exported by mysqldump.</p> <p>4.1 is about changing how MySQL works (ultimately in line to become MySQL 5) by adding additional functionality to bring it ahead of the pack.</p> <p>I'm running MySQL 5 Beta right now in a test environment, and I'm absolutely convinced that it will be the final straw that breaks oracle's back. Unlike postgreSQL, which is really the only comparable free DB platform that offers everything that Oracle does, MySQL is FAST. Most benchmarks indicate that it's faster on virtually all operations than Oracle, and the difference isn't even comparable when you're dealing with MyISAM (InnoDB has some performance penalties, but there's no way to avoid them if you want true ACID compliance).</p> You won’t see any significant improvement jumping from mysql 4.0 to 4.1 UNLESS you also upgrade to php5, and begin rewriting your code to use prepared queries.

Some people might see slight increases with full text indexes, InnoDB tables, and the general relative performance of importing data exported by mysqldump.

4.1 is about changing how MySQL works (ultimately in line to become MySQL 5) by adding additional functionality to bring it ahead of the pack.

I’m running MySQL 5 Beta right now in a test environment, and I’m absolutely convinced that it will be the final straw that breaks oracle’s back. Unlike postgreSQL, which is really the only comparable free DB platform that offers everything that Oracle does, MySQL is FAST. Most benchmarks indicate that it’s faster on virtually all operations than Oracle, and the difference isn’t even comparable when you’re dealing with MyISAM (InnoDB has some performance penalties, but there’s no way to avoid them if you want true ACID compliance).

]]>