April 14th, 2004

pinkie pie

Ok then!

Fine! Desktop meme!

Why that background? It's easy on the eyes. Occasionally I'll use a background generated by

perl -e '$x=int(rand(5))+2;$y=int(rand(5))+2;print "P3\n$x $y\n255\n";
print int(rand(128))," " for(1..$x*$y*3);print "\n";'|
pnmrotate $[RANDOM] |xv -root -max -quit +noresetroot -smooth -
instead, which I got from dagbrown.

Why is your toolbar where it is? Well, erm, it's not one, really. Menus appear when I click on the desktop. I don't use the workspace thing at the bottom at all, except as a clock.

Why the choices on your toolbar are present: Well, erm, there aren't any, really. :-)

What the desktop icons are: Absent by design.

Well, that was fun. To make up for it, I give you Hello Kitty bento.

  • Current Mood
    amused amused
pinkie pie

mysql replication

brad's mysqlcon presentation has me thinking out some of the ways we (mis)use MySQL replication at Mitel. Most of it comes down to working on elegance -- in a lot of places I think I'm doing things that work as intended, but are pretty far away from the Right Way. So now I'm trying a whole bunch of things to build confidence in the Right Way of doing things.

In doing so I have come to the following conclusions:

  • For databases of non-trivial size and indices, mysqldump is not useful, because rebuilding the indices takes ridiculously long compared to any solutions that involve copying around raw data (replication, mysqlhotcopy, stop/cp/start).
  • For replication over a WAN rather than a LAN, LOAD DATA FROM MASTER is not useful because it takes so long and so much bandwidth compared to locking, taking a local snapshot, unlocking, rsyncing to the slave, and resetting master and slave binlogs.
Thoughts? For the record, we're still all MyISAM, with our largest tables about 1.5GB (and the whole database about 5GB) and sites connected via a ~2Mb VPN over the Internet.
  • Current Mood
    contemplative contemplative