A lot has been written for and against open core now. Yet in the end, a couple tweets can catch all that is needed:
scurryn @h_ingo -- So as long as 'an open core vendor' doesn't call themselves 'an open source vendor' then everything's fine?
h_ingo @scurryn: pretty much. I think I owe everyone one more blog post to answer that question with a few more details.
(Twitter)
This is that blog post.
This is new part which contains information about what to do if problem is repeatable only when queries run concurrently.
Chapter 6. Locks and deadlocks.
In the last part we discussed how to find cause of the problem in
case
if it is always repeatable. But there are cases when problem
occurs
only under particular circumstances.
For example, such easy query can run long enough:
mysql> select * from t;
+-----+
| a |
+-----+
| 0 |
| 256 |
+-----+
2 rows in set (3 min 18.71 sec)
…
[Read more]This is new part which contains information about what to do if problem is repeatable only when queries run concurrently.
Chapter 6. Locks and deadlocks.
In the last part we discussed how to find cause of the problem in
case
if it is always repeatable. But there are cases when problem
occurs
only under particular circumstances.
For example, such easy query can run long enough:
mysql> select \* from t;
+-----+
| a |
+-----+
| 0 |
| 256 |
+-----+
2 rows in set (3 min 18.71 sec)
…
[Read more]High Availability MySQL Cookbook (Alex Davies, Packt Publishing) presents different approaches to achieve high availability with MySQL. The bulk of the book is dedicated to MySQL Cluster, with shorter sections on: MySQL replication shared storage block level replication performance tuning The recipes are clear and well explained, based on a CentOS distribution, and it seems … Continue reading High Availability MySQL Cookbook review →
Related posts:
Guerrilla Capacity Planning
Guerrilla Capacity Planning. By Neil J. Gunther, Springer 2007. Page count: about 200 pages, plus appendixes. (Here’s a link to the publisher’s site.)
Of all the books I’ve reviewed, this one has taken me the longest to study first. That’s because there is a lot of math involved, and Neil Gunther knows a lot more about it than I do. Here’s the short version: I’m learning how to use this in the real world, but that’s going to take many months, probably years. I’ve already spent about 10 months studying this book, and …
[Read more]We recently held a dedicated MySQL Track at ODTUG Kaleidoscope 2010 conference for 4 days. This is the first of many Oracle events that will begin to include dedicated MySQL content.
If your attending OSCON 2010 in the next few weeks you will see a number of MySQL presentations.
MySQL will be represented at Open World 2010 in September with MySQL Sunday. Giuseppe has created a great one page summary of speakers. This event is described as technical sessions, an un-conference and an fireside chat with Edward Screven. I’ve seen tickets listed at $50 or $75 for the day.
Open SQL Camp will be held in …
[Read more]In my post from three weeks ago, I explained why the semantics of normal ad-hoc insertions with a primary key are expensive because they require disk seeks on large data sets. Towards the end of the post, I claimed that it would be better to use “replace into” or “insert ignore” over normal inserts, because the semantics of these statements do NOT require disk seeks. In my post last week, I explained how the command “replace into” can be fast with TokuDB’s fractal trees. Today, I explain how “insert ignore” can be fast, using a strategy that is very similar to what we do with “replace into”.
The semantics …
[Read more]
I am very excited to announce that the the FINAL 1.5 version of
the InfiniDB Community Edition is now available for use.
Thanks to everyone in the community for helping us through the
alpha, beta, and RC cycles to the 1.5 release of InfiniDB.
We've put a lot of hard work into this release and we've come a
long way since 1.0. Here's a reminder of a few of the
features that have been added since 1.0:
High-speed subqueries.
Support for running on...
MySQL has supported prepared statements since version 5.0,
but the use of the non-prepared statement API is still much more
popular. Here, I'll explain what prepared statements are in
short, and show some examples and why you would, and would not,
use them.
The concept of a prepared statement is that it a SQL
statement that is lacking any parameters or literals and
with these being replaced by placeholders. Then the statement is
parsed and optimized without those values, and the placeholders
are referenced to program variables. Once this is done, to
execute the prepared statement, you set the program variables to
the appropriate values and then execute the statement. You may
change the program variables referencing the placeholder values
and re-execute the SQL statement as many times as you want,
without having to re-parse or optimize the statement.
The different steps then are:
This is my 2 cents in the Open Source vs. Open Code vs.
Commercial debate. And it's a long one...
Maybe some of you reading this are offended already, but bear
with me, I'll get there. The way I see the Open Source model,
having worked with OSS at MySQL for 6+ years now, is that this is
a great way of developing software. Not brilliant, but great, but
I'll get there also.
Users of OSS, in my mind, are OSS users for one or more of three
reasons: