At a user conference in London, MySQL announced MySQL Enterprise, a departure from their existing business and development models.

Essentially MySQL will have two versions of the core product: Enterprise and Community. This is very much like RHEL and Fedora—an approach that I support. I will let Matt dive further into the business aspects, but I am in the camp that it's OK to make money from open source, at least if you are paying for the development. I would expect a bit of squawking from the community about the MySQL change, but the community version remains good news. Marten Mickos said "we'll have many things that will make the Community version have features and functions that may or may not ever make it to the Enterprise version."

MySQL Enterprise is available as an annual subscription in four different tiers (Basic, Silver, Gold, Platinum.) Existing (and new) subscribers gain access to new management tools which Marten …

Today, you will see an announcement of a new flagship commercial offering from our company, called MySQL Enterprise. I want to explain to you why we are making these changes to our business — and to the delivery of our software.

We recognise that the needs of the MySQL Community are different from the needs of commercial enterprise customers. After 11 years of producing our software, we can no longer hope that a single offering is the best solution for both Community and Enterprise users. Consequently, we are introducing two different offerings for each distinct target group.

MySQL AB today announced ?MySQL Enterprise?, a new version of its flagship commercial subscription service that includes new automated, proactive technology to help corporate users monitor and tune their production MySQL database systems.

This is the third in a series of articles on profiling queries in MySQL (the second of two demonstrations of profiling techniques, but the third article overall). In this article I’ll present the same example as in the second article, but use a different approach to show details I didn’t include. Note: I wrote this article in 2006, when I didn’t have a clear understanding of even simple concepts such as what performance really is.

This is interesting question which I thought it would be good to write about. There are obviously benefits and drawbacks for each of methods.

Smaller applications usually start with single server which has both MySQL and Web server on it. In this case it is not usually the question but once application growths larger and you need to have multiple servers you may decide ether to grow system in MySQL+Apache pairs or split MySQL And Web Server and place them on different boxes.

Generally using separate boxes for MySQL and Web Servers is rather good practice.

It is more secure - Compromising your web server does not directly give access to your database, even though most applications have enough database access permissions to be allow intruder to trash/dump data.

It is easier to analyze - Troubleshooting bottlenecks on shared boxes is more complicated compared to systems running …

Over the last two days, I’ve deleted about a dozen comments from the MySQL Manual — and received emails from about a dozen friends — all asking the same question: “When will 5.0.26 and/or 5.1.12 be released?”

Here’s how I answer the emails: “Even if I knew for sure… I could tell you, but then I’d have to kill you“.

If you’re looking for a sure source of insider info, maybe you need to look into actually being on the inside. Get yourself one of those jobs, and you’ll know what I do - maybe even more.

All I can say is that 5.0.26 will very definitely happen Real Soon Now™, and 5.1.12 shouldn’t be far behind.

In the meantime… keep watching those mirrors.

This is the second in a series of articles on profiling queries in MySQL. In this article I'll demonstrate the technique I described in the first article.

Even when it is being repeated once more it is not true: Stripping binaries using the ‘strip’ utility can also significantly reduce the memory footprint of the application claims John Coggeshall.

While it is true that a file is smaller on disk after a strip, a quick run of "size" on a binary will show you that the actual binary part of the file is unchanged. Let's have a quick look at /proc/pid/maps to understand what happens.

Continue reading "Notes on VM"

I was looking forward for this feature for last 3 months! And at last, it is there! Now, nginx works on our streaming servers perfectly and flv streaming will not be Lighttpd’s unique feature anymore. This post is about how to use new Nginx module http_flv_module introduced in 0.4.7 (but there was a bug in its implementation, that can be fixed with my patch) and made completely perfect in 0.4.8.

(more…)