Following on from the announcement at the MySQL conference where Sun and Kickfire jointly announced data warehousing benchmark records, we have just announced new TPC-H benchmark records. Specifically, the Kickfire Database Appliance 2400 is the highest price/performance offering at 300GB, again breaking the $1 barrier for the first time coming in at 89 cents per QphH (Queries per hour on the TPC-H benchmark). The 2400 is also the highest performance (non-clustered) offering at 300GB.

I’m not going to further dwell on the numbers in this post other than to quickly point out another aspect of this achievement that Justin noted in his blog related to the energy savings the Kickfire …

I've coded and pushed wl3600++ to telco-6.4
- lots of code simplification
- lots of "duplicate" code removal

Also merged it into table-reorg clone.
And now system restart just started magically working.
So I can again run mysql-test-run

Will now fix any problems found by mysql-test-run.pl

---

I have just released version 0.5.1 of Q4M, a message queue that acts as a pluggable storage engine of MySQL. In the release, I have fixed two bugs that might that might block table compaction from occuring, or cause a return of an empty result set when data exists. Thanks to Brian for pointing them out.

Q4M Hogepage

PS. If you have installation problems, using the svn version might help. Installation problems in 0.5.1 have been fixed (link error on linux/x86_64 and installation directory problem with binary distribution of mysql).

If MySQL in Tokyo is on floor six, who is on floor seven?

?????Memcached and MySQL?

????????????????????????????Memcached ??Web?
??????????????????mixi?Facebook?LiveJournal??????
??????????????????????????????????????
???MySQL ?????Memcached ??????????????????????
???Memcached???????/???????????????????????
???????????????
????????????????????????????????????
Memcached ????????????????

?????: Brian Aker, MySQL Director of Technology
????????: ???????? ??????????????????
????: 5?23?(?) 15:00-17:00 ??:14:30
????: MySQL ????????????????????
150-0013 ?????????1??13-6 ??? IS ?? 6?
??????????????

??????????????????????????????????????
????????????

??????????????????????????????????????
?????????????

????????:
…

Last friday I had a chance to give a talk at YAPC::Asia 2008 on the internals of Pathtraq, one of the largest web access stats service in Japan.

The talk covered from techniques we use for compressing data on MySQL tables, our cache architecture, and a mysql-based message queue (Q4M) that we developed and use.

The slides of the talk are available at http://www.slideshare.net/kazuho/yapcasia-2008-tokyo-pathtraq-building-a-computationcentric-web-service, so please have a look.

Last week I was working with a client that rediscovered a bug where setting expire_logs_days and issuing a flush logs causes the server to crash. It’s MySQL Bug #17733 if you want to have a look. Seeing MySQL crash was enough inspiration to fix something that I and others have wanted to fix in MySQL for years.

Currently a flush logs command tries to flush all of the following logs in order:

• General Log
• Slow Query Log
• Binary Log
• Relay Log
• Store Engine Logs (If available)
• Error Log

The reason I wanted to fix this is because my client was issuing a flush logs to rotate the error log on a server with no replication. The crash was caused by replication. With individual flush logs it’s less likely for this to happen again in the future. People can simply issue a query for the …

Instructions for adding a new Unicode collation

By Alexander Barkov and Peter Gulutzan
Copyright (c) 2007 by MySQL AB
All rights reserved

[ Previously published as a note on a bug report.]

MySQL offers 42 built-in collations (sets of rules
for comparison and sorting) for the Unicode character
sets utf8 and ucs2. But you can add your own.

We will describe here how to add Vietnamese Unicode
collations. This is intended as an example, so
that you can try out all the steps and then modify
based on your own rules for some other language.
We chose Vietnamse because many people asked for it
via our "Feature Request" option in bugs.mysql.com,
http://bugs.mysql.com/bug.php?id=4745.

There are two ways to add a new collation:
* Change the source code. This is the trickier way,
but it's the only way for pre-August-2007 versions.
* Change the LDML "markup" file. This hasn't been
tested much, but it's simpler, it requires no
recompilation. (LDML stands for …

# Enable some colors
alias ls="ls -G"
# Gimme details and size in KB, MB or GB, I'm not good reading bytes
alias l="ls -lh"

# SSH aliases
alias moe="ssh moe.warp.es"
# I always misspelled that one 
alias mow=moe
alias ebox="ssh root@ebox"
alias amedias="ssh amedias.org"
alias rssh="ssh -l root"

# Git alias
ci="git ci" # Formerly svn ci
# Jump to github from repository
alias github="git config -l | grep 'remote.origin.url' | sed -n \
's/remote.origin.url=git@github.com:\(.*\)\/\(.*\).git/https:\/\/github.com\/\1\/\2/p' \
| xargs open"

# MySQL
alias myserver="sudo /usr/local/mysql/support-files/mysql.server"

# Start webserver on localhost:8000 sharing current directory
alias webshare='python -c "import SimpleHTTPServer;SimpleHTTPServer.test()"'

# Rails server
alias ss="./script/server"
alias sss="screen ./script/server"
alias sr="screen -r"

AdBrite has signed off the release of my materialized view maintenance stored procedures under the GPL. LGPL is also an option, and I'm curious as to which you feel is more appropriate for a set of stored procedures that are never rendered into bytecode, or technically linked with other source. Is GPL acceptable or is LGPL more appropriate?

I am waiting on the approval of a sourceforge project to release the source code. Over the weekend I put together a series of web pages for the project, which I plan to call 'Flexviews for MySQL' which will also be hosted on sourceforge.