About 250 MySQL/Sun engineers are meeting in Riga, Latvia, for the annual internal MySQL Developers Meeting. 250 sounds like a large number. And a group picture is quite impressive.
Today is Software Freedom Day, which is organized at the local university, and includes talks by Mark Callaghan (Google), Mårten Mickos (MySQL), Domas Mituzas (Wikimedia Foundation).
The full program also mentions free beer, which is an irresistible combination!
Man, what did I do before strtotime(). Oh, I know, I had a 482 line
function to parse date formats and return timestamps. And I
still could not do really cool stuff. Like tonight I needed
to figure out when Thanksgiving was in the US. I knew it
was the 4th Thursday in November. So, I started with some
math stuff and checking what day of the week Nov. 1 would fall
on. All that was making my head hurt. So, I just
tried this for fun.
strtotime("thursday, november ".date("Y")." + 3 weeks")
That gives me Thanksgiving. Awesome. It is cool for
other stuff too. At its very basic, it can take a MySQL
datetime field and turn it into a timestamp. Very handy for
date calculations. It also understands RFC 2822
and ISO 8601 date formats. …
The 1.0 Alpha of Tungsten Replicator is out. Actually it's been
out since Tuesday but it's been a busy week. Binary downloads are
available here.
The Alpha release offers basic statement replication for MySQL 5.0 on Linux, Solaris, MacOSX, and Windows
platforms. The setup is very simple, and there are procedures for
master failover as well as performing consistency checks. If you
work at it, you'll find bugs. That's a promise, not a threat.
Please log them in the project JIRA. We gladly accept feature
requests, too.
Meanwhile, the …
I haven’t posted any update in 2 months not because I haven’t been doing anything but rather the opposite: I have been exceptionally busy. As Baron has noted, I work with Percona doing the maintenance and development for Maatkit, of which release 2325 was just published. Consequently, I haven’t been working on my own scripts, though hopefully that will change, and in some ways it must. Here’s what I have in mind for my own scripts:
mysqlsla: I’m going to create a hybrid between this and mk-log-parser. Whereas mysqlsla does some things that mk-log-parser doesn’t, mk-log-parser has a better, more maintainable code base. Furthermore, I’m currently working on other log handling code which will affect some future plans I had for …
[Read more]Welcome to the 115th edition of Log Buffer, the weekly review of database blogs.
I must thank Paul for taking over at last minute for LB#114 last week, when, as he put it, “ . . . a killer combo of painkillers and the pain that the painkillers can’t kill . . . ” reduced to me a less-than Log-Buffer-capable state. Or to be more precise, to a writhing, benighted gargoyle of misery. (Too colorful?)
Anyway, the good news is that I’m better. Not all better, mind you. Between the tooth thing and my spending all my working time on a special project, there was nothing left for poor old Log Buffer. So, I face the choice: throw it open to you, LB’s loyal …
[Read more]
Before I leave Grazr to work at Lycos, I've been tasked with
documenting several things-- MySQL setup, including replication,
nagios, UDFs we use, etc. I was describing on our wiki what using
InnoDB means, and some basic things about settings. Here's a
tidbit of it that I think is useful information.
Some important InnoDB Characteristics
InnoDB stores data and files in the same place whereas MyISAM has
separate index and data files. InnoDB stores it's data in either
a single tablespace file (ibdataN -- n being number) which
containins all tables, or a single auto-extending tablespace file
set by innodb_file_per_table (tablename.ibd), which is what we
use for grazr because file-per-table allows OPTIMIZE TABLE to
reclaim space from deletions, would could gives better
performance with better optimized tables. Also allows you to
restore backups of single tables without interrupting the use of
the remaining InnoDB tables (per …
Open source software and data warehousing go together like beer and pretzels READ MORE
I had a lot of good experience using fabforce's DB designer. Now
that I upgraded to mySQL workbench, I have nothing but good
things to say.
In 5 mins I was up and running after install. I took my mysqldump
of my schema
mysqldump -d --no-add-drop-tables
Clicked File->Import->Reverse Engineer MySQL Script
Tada a picture of my schema.
Pictures are always nice to represent what your conveying to
individuals who may not be as experienced with the db structure
as yourself. Just for this feature alone I recommend using Work
Bench.
Let me first start of with the disclaimer, that I do not use
memcache to scale, I use it to reduce latency. I'm of firm belief
that the database layer should be able to handle the requests,
while memcache is used to keep frequent requests returning in a
consistent time frame i.e. reduce I/O spikes.
Capacity planning is key to making sure your site can serve the
requests to users. If the site is slow, or down that is loss
revenue in any revenue model used to monetize your product.
How to determine when you need to add more memcache
servers.
The stats I look at are system stats and memcache stats.
Memcache is Memory / network heavy. CPU spikes are very low, and
if the CPU starts maxing out that is probably due to some sort of
network driver issue or huge context switching or large values
stored in memcache.
So on the system side I look at vmstat
Download Maatkit
There’s a new release with a lot of goodies — speed, efficiency, user-friendliness, and new features. In particular some of Percona’s clients have sponsored features for things they need such as the ability to more frequently verify that slaves are in sync with their masters. If you need features, please ask Percona [...]