Slashdot Mirror
MariaDB vs. MySQL: A Performance Comparison
Nerval's Lobster writes "MariaDB is a fork of the MySQL source code, split off in the wake of concerns over what Oracle would do with MySQL licensing. In addition to its role as a 'drop-in replacement' for MySQL, MariaDB also includes some new features that (some claim) make it better than MySQL. Jeff Cogswell compares MySQL and MariaDB and suggests (in his opinion) that there's 'more than enough reason to ditch MySQL and switch over to MariaDB and stay there.' Why? While he breaks down MariaDB's new features and thinks many of them aren't that fantastic, and while MariaDB's performance isn't that much better than that of MySQL ('MariaDB's performance appears a bit better on multi-core machines, but I strongly suspect that one could tweak MySQL to match'), the questions over Oracle and MySQL licensing give him pause. 'MariaDB shows every indication that it will be around for quite awhile, while you can't really say the same of Oracle's MySQL,' he writes. 'Free-and-open MySQL competes with Oracle's proprietary and extremely competitive tools. That alone is grounds for concern — will Oracle do something to impede MySQL's development?'"
I think concerns about Oracle's long-term plans for MySQL are valid to ask.
If it isn't making Larry money, what did he buy it for and what is he planning to do with it?
Oracle isn't exactly a customer friendly company (just ask anyone who had an older Solaris machine when Oracle bought Sun and got told they needed to buy a support contract to even access docs), so I've always wondered why they would buy a free database and continue to develop it and give it away.
If I was choosing based purely on open-ness, something which doesn't have the chance of Oracle coming along and closing it otherwise strong-arming people would be a plus.
I guess it legitimately is FUD, but sometimes, there's valid reasons to mistrust such entities. And having dealt with Oracle over the years, they themselves are a very strong reason to be suspicious.
Lost at C:>. Found at C.
They did. In short they stopped providing test cases for new features. Do not use MySQL. Period. Read more about in here.
I think concerns about Oracle's long-term plans for MySQL are valid to ask.
If it isn't making Larry money, what did he buy it for and what is he planning to do with it?
Oracle isn't exactly a customer friendly company (just ask anyone who had an older Solaris machine when Oracle bought Sun and got told they needed to buy a support contract to even access docs), so I've always wondered why they would buy a free database and continue to develop it and give it away.
If I was choosing based purely on open-ness, something which doesn't have the chance of Oracle coming along and closing it otherwise strong-arming people would be a plus.
I guess it legitimately is FUD, but sometimes, there's valid reasons to mistrust such entities. And having dealt with Oracle over the years, they themselves are a very strong reason to be suspicious.
Oracle maintain multiple open source initiatives. *I'm * not making any claim about wether these are maintained 'correctly or not, because the truth is that I am not in a position to state factually what the true state is.
But - people still use Virtual box. People still use Java. People are still using MySQL.
I'll pitch - even though I struggle to think its true - that if Oracle maintained them well, and if a true state exaists where the smaller MySQL may lead to an upgrade when things get large to Oracle DB - I can see why a vendor might say to itself that damaging our own product isn't productive. If they trust us implicitly doing a good job on MySQL they will believe the same basic premise on the day they need heavier iron and DB.
It is understandable commecially to look at things and remove or kill things that are done and have a fork in them. Its another to just vandalise in an unthinking stupid way a well grounded, popular and well regarded product.
The core question got asked at the end of the first post:
That alone is grounds for concern — will Oracle do something to impede MySQL's development? Citation and real evidence required.
The real world, true answer to that question is the real guide, other stuff and argument is fluffy..
We`re all equal
The longer you wait, the less chance there is of it still being a 'drop-in replacement'. Both sides are likely to make incompatible changes to the database format, and while that's OK when you're running a 1GB database that you can just dump out and restore, it's a problem when you're dealing with 60TB of data.
My favorite part is that the article is titled "MariaDB vs. MySQL: A Performance Comparison", but since the performance is almost identical they spend most of the summary talking about ideological differences. I guess "MariaDB vs. MySQL: An Ideological Comparison" didn't have the same ring to it.
E pluribus unum
MariaDB is taking the MySQL code via the GPL and then building on top of it with new code. Those changes are all having their copyright assigned to MariaDB, and in some cases the GPL will also require a public release. Eventually MariaDB is expected to have a non-trivial set of improvements, and the copyright ownership of all the new code will be to MariaDB. That allows selling the combination of GPL core plus some explicitly owned private code, the exact same way MySQL was sold to Sun.
This is the same scam that let Monty cash out once already, using the work of open source contributors who assigned their copyright to his original company. No reason he can't do it again, if people are gullible enough to fall for it twice.
I have done some tests some months ago, and I checked that MariaDB solves some problems that MySQL has. The performance is similar using simple queries, but when you write complex queries with subqueries, lots of joins and more, then MariaDB demonstrates the power of their code. I posted an entry in my wiki of the SaltOS project explaining how MariaDB helped to my project:
- http://www.saltos.net/portal/en/wiki/75/why-use-mariadb-instead-of-mysql.htm
Josep Sanz.
The SaltOS project.
How is Oracle crippling MySQL?
By just sitting on it, and not improving it.
Years ago, MySQL lacked many features that kept it from being a "real" database. Over the years, it has added transactions, stored procedures, triggers, etc. If that trend continued, why would anyone use Oracle? If Oracle just shut down MySQL, the momentum would shift to PostgreSQL or MariaDB. So by keeping MySQL alive, but stopping the improvement, Oracle is holding back free alternatives from competing with them.
Not to mention the whole thing ignores the elephant rotting in the corner, that old Monty makes anybody working on MariaDB sign over their code so he could pull the same trick twice and sell it out from under them just as he sold MySQL.
Now don't get me wrong, I think Monty has big brass balls to be able to pull what he did last time and get away with it, he made them think they were actually buying a product in MySQL and in reality all they got was the name and the website, he ended up walking away with the code AND the customers, how he got them to buy without a do not compete I don't know but it took some big brass ones to pull it off.
But like the old saying goes "fool me once.." what is to stop Monty from pulling the same game with MariaDB? Nothing that I can see, he still has it set up so no matter who works on it HE owns the code, which means he can do whatever he wants with it. Now maybe he scammed enough off the last sale that this won't be appealing, maybe not, would you really want to take that chance?
ACs don't waste your time replying, your posts are never seen by me.