This week I’ve been writing based on my linux.conf.au 2014 talk, which you can watch the recording of.[Read more...]
|Showing entries 1 to 30 of 34||Next 4 Older Entries|
Warning: this is a mixture of historical content, biases, stupid marketing and unknown/proprietary/closed source technologies. Proceed with caution.
NuoDB marketing was sending out this message, encouraging me to blog (they were looking for bloggers too):
And while Facebook sharded MySQL 4000 times, even they call it a “fate worse than death.”
We’ve seen this phrase before and it did not come from us. For whatever reason NewSQL echo chamber is repeating this with less and less truth in it. In various whitepapers (all behind registration walls) they mention some analyst estimates and try to put a parallel between operating costs of large companies and something a new developer would do, as if everyone is living under same constraints.
I don’t know if NuoDB is a good technology for the[Read more...]
This is one close to my heart. I’ve recently written on other storage engines: Where are they now: MySQL Storage Engines, The MERGE storage engine: not dead, just resting…. or forgotten and The MEMORY storage engine. Today, it’s the turn of MySQL Cluster.
Like InnoDB, MySQL Cluster started outside of MySQL. Those of you paying attention at home may notice a correlation between storage engines not written exclusively for MySQL and being at all successful.
OpenSQL Camp Portland 2009 is coming up on the 14th and 15th of November. Eric Day (of the Drizzle project) is the lead organiser this time around.
I went to the first edition in Charlottesville VA last year which was organised by Baron Schwartz (Percona). It was a great event, like other unconferences but with specific focus on database technologies. Monty (MySQL), Brian (Drizzle), Richard (SQLite), Jim (Interbase/Firebird/Falcon), Bruce (PostgreSQL) were all these, as were various storage engine builders. Very interesting, and lots of informal fun. If you’re anywhere near, do go!
Even though noone from our gang is able to make it to this one, Open Query is sponsoring this event – for all the above reasons. It rocks and deserves every support.
Keep it. Make sure it gets correctly positioned in the coming months.
It appears that with the Oracle acquisition, the reason-to-exist for Falcon is regarded as gone (a non-Oracle-owned InnoDB replacement), previously seen as a strategic imperative - much delayed though.
But look, each engine has unique architectural aspects and thus a niche where it does particularly well. Given that Falcon exists, I’d suggest to not just “ditch it” but have it live as one of the pluggables. What Oracle will do to it is unknown, but Sun/MySQL can make sure of this positioning by making sure in the coming months that Falcon works in 5.1 as a pluggable engine, perhaps also creating a separate bzr project/tree for it on Launchpad.
Then the good work can find its way into the real world, now.
The following was in the just released monthly bug report for the Falcon storage engine:
“With the news that Sun has aggreed to be purchaced by Oracle, Some inevitable changes will occur. Once the acquisition is made, the need for Falcon as a MySQL storage engine will be re-evaluated. Until then, Falcon will continue to improve stability and performance. The team will also evaluate other technical niches that may be unique to Falcon.”
I for one would be very disappointed to see Falcon not supported by Oracle. I know they have worked very hard to create a next-generation storage engine. While it could be argued that InnoDB can fill all use cases, I believe that choices are a good thing and having one less choice is not a good thing.
Good luck all on the team. You have been nothing but kind and generous when answering my dumb questions via email and in person. You can count my vote for “keep it!!”.
A while ago I posted about a comment a Sun performance engineer made about a scalable replacement for InnoDB. At the time, I did not believe it referred to Falcon. In hindsight, it seems even clearer that the Sun performance experts were already working hard on InnoDB itself.
Sun’s engineers have shown that they can produce great results when they really take the problems seriously. And I’m sure that InnoDB’s performance has untapped potential we don’t see right now. However, it does not follow that their work on InnoDB is what was meant by a scalable replacement for InnoDB. Or does it?
General-purpose MVCC transactional storage engines with[Read more...]
The second public alpha version (1.0.14-alpha) of HoneyMonitor Audit Pro - the Edition of the HoneySoftware’s GUI for MySQL™ mainly oriented to Server Administration, Monitoring and Tuning - will be released soon.
In this article I’ll try to describe the new features implemented and the most important bugs fix of this version.
You will find the complete list of bugs fix and improvements in a next post - when we will release v.1.0.14-alpha - and in the Release Notes File included in the build.
Your questions, enhancement requests and comments are welcome.
A. New Features
1. Audit System
1.1.1. STMT - New connection Option
1.2. Support for the Maria Engine
1.3. Other bugs fix
2. Performance Reports
MySQL® 6.0.5-alpha, the latest version of the 6.x branch of the Database Server, is available for download from the SUN|MySQL Web Site.
Metadata (data about the data) are very important, especially for software developers. In this article we will see what’s new in FALCON metadata handling doing some comparison with the old 6.0.4-alpha version.
New tables in the `information_schema` database
As you know, the source for metadata is the database `information_schema`. To start, let’s see which tables related with FALCON metadata are included in that database:
mysql> SELECT VERSION();
Jim Starkey, the well known database architect, author of Interbase and Netfrastructure, is leaving MySQL.
Jim's company was acquired by MySQL two and half years ago, to help creating MySQL new transactional engine, Falcon.
Zack Urlocker, reports on the event and says that Falcon is still on track and he is confident that it will be a success.
The reason is that isolation between concurrent transactions cannot be guaranteed, meaning that two concurrent transactions are not guaranteed to be serializable (the result of a concurrent transaction that has committed can "leak" into an ongoing transaction). Since they are not serializable, it means they cannot be written to the binary log in an order that produce the same result on the slave as on the master.
However, when using row-based replication they are serializable, because whatever values are written to the tables are also written to the binary log, so if data "leaks" into an ongoing[Read more...]
Yesterday, during the talk of Ivan Zoratti, at the meeting with Marten Mickos and the Italian Team of SUN | MySQL in Rome, there was a question about Falcon performance: a guy pointed out that InnoDB is better than Falcon.
Well, this is not really the truth.
How many processors are you using for Falcon benchmarking?
Falcon is designed to make optimal use of modern large-memory multi-CPU/multi-core hardware. So when comparing performance of Falcon and InnoDB, you can’t leave this out of consideration!
Please, see the shoots below:[Read more...]
From May 28th-31st, the annual LinuxTag will take place in Berlin, Germany. I followed the growth and evolution of LinuxTag from the very early days and I have fond memories of the event back when it still took place at the University of Kaiserslautern and our SuSE "booth" was just a regular table taken from the lecture rooms...
Things have evolved a lot since then. Today, LinuxTag is one of the largest Linux/Open Source Events in Europe and my new employer Sun is a major sponsor this year. In addition to several talks and keynotes, there will be a large Sun booth in the exhibition area (Booth #205) and we will have a dedicated MySQL demo pod! Some of the things we plan to demo there are the upcoming MySQL Server releases ([Read more...]
This article describes how to install the Drupal 6.2 CMS on MySQL (http://mysql.com/) 6.0, using the Falcon Storage Engine. The operating system is a default Ubuntu 8.04 "Hardy Heron" (x86) installation.
I will make a few assumptions here, in order to keep the instructions simple: a fresh OS install, no other MySQL databases or web services are running or have already been installed. Both MySQL and the web server are installed on the same host. You should be able to become root to install packages and to have access to the local file system and[Read more...]
Hakan Küçükyilmaz has just posted a new article about the Falcon Engine.
There he explains that the Falcon Team at MySQL AB has added this week six new tests to the Falcon test suite and he reports (as usual) a time-trend chart of failed and passed Falcon tests.
I have calculated the ratio failed/passed tests and we can see that it is improving:
9% | (17:190) | 207 tests in total | the last week
10% | (19:182) | 201 tests in total | two weeks ago
Of course the ideal ratio is 0% i.e. 0 test failed.
In that post Hakan was wondering where and how Users use the Falcon Engine, what features they like/not like[Read more...]
Day two of the conference was a little disappointing, as far as sessions went. There were several time blocks where I simply wasn’t interested in any of the sessions. Instead, I went to the expo hall and tried to pry straight answers out of sly salespeople. Here’s what I attended.
This was a talk focused on how MySQL has made it possible for community members to contribute to MySQL. There was quite a bit of talk about IRC channels, mailing lists, and the like. However, the talk gave short shrift to how MySQL plans to become truly open source (in terms of its development model, not its license). I think there was basically nothing to talk about there. I had a good conversation about some of my concerns with the speaker and some others from MySQL right afterwards.[Read more...]
Here is the quick notes from the session Falcon from the beginning by Jim Starkey and Ann Harrison
The solidDB for MySQL database engine for MySQL may have lost its sponsor following IBM’s acquisition of Solid Info Tech but events at this week’s MySQL Conference and Expo prove the certified engines program is alive and well.
Kickfire has recently[Read more...]
As followers of Free / Open Source Software know, there are several ways of being free.
As for free as in speech, look for Wednesday’s keynote at the MySQL Users Conference here in Santa Clara on the US West Coast. It’s by Rick Falkvinge, party leader of the Swedish Pirate Party. Or download MySQL Community Server, it’s free as in speech.
As for free as in beer, sure, again, just download MySQL Community Server, install it, and use it. Old news.
But what if you’re lazy enough not to want to download and install MySQL Server? What if you just want to use an instance of MySQL Serer, installed and provided by someone else, with a simple command like
mysql -h db4free.net -P 3307 -u [username] -p[password][Read more...]
I’ll be following closely the progression of Storage Engines available in the MySQL Database server, well soon to be available when 5.1 gets to GA (hopefully by end of Q2 which is what we have been told). Tick, Tick, time is running out.
PrimeBase XT (PBXT) and Blob Streaming is obviously my clear focus, actually now working for PrimeBase Technologies, the company which I want to note for people is an Open Source company, committed at providing an open source alternative to the other commercial players. You also have at the MySQL Conference talks on the the existing InnoDB from Innobase (a subsidiary of market RDBMS leader Oracle). There is a[Read more...]
A year ago, I criticized the under-development Falcon storage engine in MySQL 6.0 of failing to meet the demand of large-scale deployments. Falcon has now reached a beta phase and is included in the MySQL 6.0 alpha versions, most recent release of which is 6.0.4 this February. We're thinking of making an early test of Falcon in place of MyISAM/InnoDB for Habbo to see what to expect later on, so I reviewed the documentation again, and thought to look at my concerns from a year ago.
Falcon now supports multiple tablespaces per database, although the corresponding manual page still begins with the unfortunately misleading sentence of "all data ... is stored within a single[Read more...]
While MySQL 5.1 is almost ready, MySQL 6.0 is already in alpha with many new features, including a Beta of Falcon. Falcon (Intro (http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php), White Paper (http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php)) is designed for typical Web 2.0 workloads in modern (i.e. many cores, large memory) machines.[Read more...]
Today Robin Schumacher, MySQL's Director of Product Management, announced that the mysql Falcon storage engine has moved into a beta release stage. Falcon, a new transactional storage engine introduced in mysql 6 (aka 5.2), has been in alpha for years. Other popular storage engines include MyISAM, InnoDB, which Falcon is supposed to challenge (successfully? :-/), and the upcoming[Read more...]
With 130 entries in the “MySQL” category and no MySQL-related subcategories, my blog had become impossible to search and navigate easily.
And thus I created a number of new categories for the MySQL entries within my blog. They’re listed in the left navigation bar, below the months, as well as below:[Read more...]
MySQL has introduced Previews as a new way of delivering features for early testing by our community.
Previews are for testing of features, not of versions. The two previews we offer today are the Falcon Feature Preview based on 6.0, and the GIS Feature Preview based on 5.1. However, the version number as such is not intended by us to set any expectations on when the feature will be in a production version. For instance, Falcon is going into the 6.0 code base, but the GIS geographical data won’t be in before 6.1 (although the preview is based on 5.1).
Previews are by definition a bit[Read more...]
If you are not familiar with tablespaces you may be wondering what the big deal about them is. Tablespaces are a logical addition to a database that helps maintenance, and potentially, can improve performance.
In Oracle and MySQL, a tablespace is a logical unit meant to store segments (i.e. tables and indexes). In Postgres, a tablespace is a physical unit. It is a symbolic link to a directory. Postgres does not allow tablespaces on operating systems that do not support symbolic links (such as windows).
The data file is the actual physical storage mechanism in Oracle and MySQL. Postgres stores tables in individual files. Postgres support of tablespaces is minimal. In MySQL and Oracle, performance can be improved by a more granular spread of data across disks. Ease of maintenance is maintained due to the logical grouping of
|Showing entries 1 to 30 of 34||Next 4 Older Entries|