MySQL 5.5 delivers significant enhancements enabling users to improve the performance and scalability of web applications across multiple operating environments, including Windows, Linux, Oracle Solaris, and Mac OS X. The MySQL 5.5 Community Edition, which is licensed under the GNU GPL, and is available for free download, includes InnoDB as the default storage engine.
What happened to the $5000 licensing cost for InnoDB? Was that only for the commercial edition? I thought I read somewhere that it was wasn’t going to be available for free…
As of right now, even the low end commercial editions that start at $2000/year include InnoDB and MyISAM. There’s also MySQL Embedded that’s targeted at OEM’s and ISV’s, and that has separate pricing that isn’t disclosed on their website. I’ve never had reason to use anything other than the Community Edition, so I’m not sure what pricing on Embedded looks like.
Edited 2010-12-16 22:30 UTC
the speed gains on Windows using multi core chips are pretty substantial. Good job guys!
I’ve spent some time in computer science research and that assertion is … in my book (fill in the blank as you wish, my English is not good enough to have the appropriate word/phrase other than “a lie”).
Wow, how is that even possible? 1500 percent gains means 15 or 16 times the time needed for the same RW operations… which seems very strange to me. Either 5.1 was purposely badly coded or numbers are inflated or they’ve done some incredibly awesome engineering work. In which case, they should pass the appropriate info to Microsoft to make the future Windows OSes faster than they would have been.
Anyway, it’s good that Oracle didn’t kill MySQL.
MySQL has long been optimized for Nix based systems.
<Wow, how is that even possible
It is possible by eliminating context switches and kernel transitions. As for the numbers, do not forget this benchmark (sysbench) does not resemble reality in anyway, it is just hammering server with similar queries from 256 clients.
To tell the truth, this was an easy one, and the one that should have been done years ago. What brought the main speed gain inside Innodb, was replacing OS mutex (the slow one, used to synchronize between processes) with CRITICAL_SECTION. That would have worked even on Win95. The fact it was still inside is quite embarassing (it shows basically that this thing was not profiled since Heikki has written it in the mid 90ties) . The rest of Windows adjustments were switching to Vista conditions (for Innodb’s os_event) and rwlocks (not innodb , this is inside the core server), when possible. Compliment to Windows division at Microsoft, those new synchronization primitives are extremely well tuned.
Thank you, Oracle, for this fine database! Nice to see it’s not dead yet.
PostgreSQL is better.