May 2 2009

OSCON 2009 Here I Come

After having so much fun at the MySQL/Percona 2009 conference, I’ve decided to self-fund my trip to O’Reilly OSCON 2009.

My first step in this was adding banner ads to fewbar.com. I’ll also be juggling swords and old 386 laptops on Venice Beach on the weekends just in case my traffic doesn’t increase.


Apr 30 2009

Decision vs. Precision

I love Seth Godin’s blog. Its technology aware but focuses people, which is why we have this technology, right?

Anyway, he makes the point in his latest post titeld “I need more time” that more time doesn’t necessarily lead to better decisions.
› Continue reading


Apr 27 2009

Percona Performance Conference/ MySQL Conference 2009

Seated in the terminal here at San Jose airport, I’m reflecting on a really great couple of days spent at the Santa Clara convention center. In addition to publishing the working DBD::drizzle driver, I met a lot of very cool people, and heard some really great talks.

Big thanks go to Patrick Galbraith, who not only handled the dirty work of publishing DBD::drizzle to CPAN, but also handled the dirty work of introducing me to the likes of Brian Aker (founder of the Drizzle project), David Axmark (co-founder of MySQL), and a bunch of other really smart people.
› Continue reading


Apr 22 2009

DBD::drizzle w/ libdrizzle is a reality

After a few weeks of working hard on it, myself and Patrick Galbraith have gotten DBD::drizzle working using the new libdrizzle.

Patrick is uploading it to CPAN right now, but you can get the latest version in my Launchpad tree. I have tested it running MogileFS as well, which seems to work perfectly.

For now its just a near direct port from libmysqlclient to libdrizzle.. but we are planning on revamping a few of the things to handle multiple connections and fully non-blocking I/O. w00t.


Apr 22 2009

At the MySQL/Percona 2009 Conference

I’m seated in rooms 203/204 of the Santa Clara convention center, listening to Eric Day’s talk on Gearman, a very cool technology for asynchronous distributed job queueing. Anyway, the point is, I’m here at the conference, wandering around. If you see me, come by and say hi. Here’s what I look like today…

Me at the MySQL/Percona conference


Mar 25 2009

MemcacheDB fault tolerance procedures

It semeed so simple, just setup two memcachedb instances and point them at eachother. Instant fault tolerance, Right? If only it were so simple!

Its not entirely clear from the documentation how to setup memcachedb for fault tolerance. Here’s the procedures I’ve found useful.
› Continue reading


Feb 9 2009

Facebook’s scribe makes a meal out of me, and comes back for more

So, I was working on getting Facebook’s seemingly amazing Scribe logging architecture setup to check it out. One of the requirements it has is ‘fb303′, which is included with Thrift in the contrib directory. I ran into this:
› Continue reading


Dec 14 2008

Memcached and Mogile Form MemcacheMegaZord!

So I was starting to play with Memcached for session storage, and I found a fairly big problem with justing memcached in its normal caching mode as a session store. It really just boils down to caching and storing of deterministic data being very different things that only look similar on the surface.
› Continue reading


Nov 11 2008

I should write an innodb backup tool

One of my favorite bloggers, Peter over at Percona/MySQL Performance Blog, has thrown down the gauntlet. Basically saying that it would be fairly trivial to write an incremental InnoDB backup tool.

If you see me, and I haven’t run up to you and told you that I am writing/have written an amazing InnoDB incremental backup tool, I give you permission to make fun of me. This sounds like a fun, interesting project that will challenge me and sort of scratches an itch I have, which is, faster MySQL backups.


Oct 4 2008

Deciding whether to send reads to slave or master

There are quite a few articles out there that talk about how to give your application some context and send reads to one server, and writes to another. There are even some mentions of marking your connection “dirty” and then sending all reads to the write server.

As a first try at scaling things, I recently made a change to our web application’s data access layer where reads went to a group of readonly slaves. However, if a write was made to a database, a value was put into the user’s session, saying that the database was dirty, and causing all subsequent reads to go to the master server.
› Continue reading