Out of time, finally getting tired. Tomorrow, for sure :) One
last bug to hunt down.
For now, HEAD's looking pretty good. grab the export
tarball, check out the git repo, etc. If you're bored.
The most interesting addition is the CMake build and the fact
that DPM's now portable to at least four operating systems. I've
read Jan's recent posts on the subjecft of build systems, and
I'll admit up front that I haven't touched DPM recently due to my
reluctance to use autotools.
I've decided CMake isn't evil enough to warrant avoiding it. It's
an extra dependency, so we'll see how it goes. There's even been
recent discussion on using lua as CMake's build language :) …
Out of time, finally getting tired. Tomorrow, for sure :) One
last bug to hunt down.
For now, HEAD's looking pretty good. grab the export
tarball, check out the git repo, etc. If you're bored.
The most interesting addition is the CMake build and the fact
that DPM's now portable to at least four operating systems. I've
read Jan's recent posts on the subjecft of build systems, and
I'll admit up front that I haven't touched DPM recently due to my
reluctance to use autotools.
I've decided CMake isn't evil enough to warrant avoiding it. It's
an extra dependency, so we'll see how it goes. There's even been
recent discussion on using lua as CMake's build language :) …
The team was on vacation during the holidays (a well deserved one I hope) and today is the first day the full team is back. Our plan is to keep our main focus on bug fixes and also start working on the plugin-writing/scripting tutorials. We also have to add more hooks at various places in the tool so people interested can add their stuff wherever it needs to be added.
Starting on the 14th of January we will travel to the MySQL company meeting and we will try hard to get a new release out before that - including as many bugfixes as possible.
Currently in the 6.0 tree we have support for Libevent. This is one of those things I've been
wanting to see
us do for years and it was finally completed a few weeks ago by
Damien
Katz (aka CouchDB) with some help from Dmitri Lenev.
So what does this do? MySQL uses a 1:1 ratio for connections
and
threads. Libevent allows us to pull threads into pools and use
them
for connections. This is pretty awesome for 8way machines
since
partially solves thread contention issues. Below is an example
of
MyISAM doing large number of inserts with the number of users
doing
inserts increasing (1-300 users). The graph shows the time taken
for
each test run. Similar numbers show up when you run benchmarks
with
Innodb (leave concurrent …
First of all, I'd like to wish the PHP & other Web communities a happy new year. 2007 has been a great year for the Web and the IT industry as a whole and I believe despite the economic worries, 2008 will be no different.
The following are some predictions I make about 2008. I'm looking forward to seeing how many of these actually come true.
Java on the Web continues to lose market share
While Java is a good platform for a variety of software tasks, I believe it has never been very good when it comes to the Web. Despite the dozens of Java Web frameworks which have promised an end to traditional Java EE suffering I believe not much has changed. Java is still a technology which is not suited for today's modern Web applications especially as it takes far too long and is far too expensive to deliver Java-based Web applications. In addition, JVM's just don't scale out as well as Apache/PHP-like solutions and the …
[Read more]
r5 of DPM will appear ... tomorrow! It's close now, but
I'ma go party a bit. There's new code in HEAD if you're
bored.
New stuff:
- Bugfixes (crash bugs, silly things)
- CMake build
file.
- Code ported from Linux to OS X (leopard) PPC, OpenBSD 4.2,
FreeBSD 6.2
- (not done yet) support INADDR_ANY, unix domain sockets, few
more things.
Also, new releases of memcached coming up as soon as possible,
along with nice clear useful documentation.
- 1.3.0, with binary protocol!
- 1.2.5, with portability fixes!
- Overview of all outstanding projects/ideas worth doing, now
that memcached's development has been jumpstarted.
Then later;
- 1.3.1, probably with all of the binary protocol bugs
fixed!
Happy new …
r5 of DPM will appear ... tomorrow! It's close now, but
I'ma go party a bit. There's new code in HEAD if you're
bored.
New stuff:
- Bugfixes (crash bugs, silly things)
- CMake build
file.
- Code ported from Linux to OS X (leopard) PPC, OpenBSD 4.2,
FreeBSD 6.2
- (not done yet) support INADDR_ANY, unix domain sockets, few
more things.
Also, new releases of memcached coming up as soon as possible,
along with nice clear useful documentation.
- 1.3.0, with binary protocol!
- 1.2.5, with portability fixes!
- Overview of all outstanding projects/ideas worth doing, now
that memcached's development has been jumpstarted.
Then later;
- 1.3.1, probably with all of the binary protocol bugs
fixed!
Happy new …
Marten Mickos sent me an update on MySQL's exceptional 2007. It makes interesting points about open source, generally, while relaying important information about MySQL. Here are excerpts from the message, with his permission:
In 2007 we continued to make free and open source software available and affordable to all. MySQL version 5 was our top download hit, expanding the universe of MySQL users further into the Web2.0 and Enterprise2.0 markets. MySQL Proxy, experimentally released in 2007, garnered the attention of scale-out experts worldwide.
Our commercial offering MySQL Enterprise was significantly upgraded with improved monitoring and other services, and we launched MySQL Cluster Carrier-Grade Edition for the most demanding telecom uses. To expand our global reach, we opened a strong APAC office in Tokyo in early 2007.
What did we learn in 2007?
...
I often hear recruiters say that they are having a hard time to
find a MySQL production DBA. Well, since MySQL is not yet that
mature as compared to Oracle, most DBAs are therefore relatively
unseasoned.
And most DBA are not into production work yet. So, what are the
experience / characteristics of a production DBA? Here are my two
cents.
1. Manages 20-30 databases which are 25-30 GB in size.
2. Knows what to do when he is on-call.
3. Understands the inner workings of MySQL. For example, does he
know what mysqldump actually do aside from backing up the data?
How will it perform with a 25 GB data?
4. Based on the 1st criteria, the DBA will be careful in writing
his queries. For example, he knows that select * from a table is
query that should be banned from MySQL.
5. Very handy with scripting languages which could be PERL,
Shell, etc. If the DBA has to update the configuration of 30
databases, …
The doorbell rang, I was almost to late .. but I still catched
the post guy before he left..
He had a package
I knew what was in the package ..
but I was even more surprised when I opened the book..
Thnx a lot folks !!