Speakers | |
---|---|
Stéphane Combaudon | |
Schedule | |
Day | Saturday |
Room | H.2213 |
Capacity | 100 |
Start time | 18:30 |
End time | 18:55 |
Duration | 00:25 |
Info | |
Track | MySQL & friends devroom |
A practical overview of Maatkit
Maatkit has saved my day more than once. In this talk, I will show you real-life examples of hard problems that I had to solve, and how Maatkit provided elegant (and most of the time very efficient) solutions.
I will cover the following short stories:
- When I run this query manually, I get an immediate answer, but when the same query is run by the application, it takes 30+s. Why?
- Did you know that the data you're backing up is not the right data?
- You say that we're running 400 SET queries/s. I doubt this, could we catch them live?
- Last time I wanted to update this field in the whole table, it took 2 weeks. Any tips to run the update faster?
- I had to skip an event on a slave. To avoid inconsistencies with the master, is rebuilding this 10GB table from scratch the only way?
- We regularly have very long queries that freeze the whole server. Could we kill them automatically if they run for more than 50s?
And a few more if time permits.
Maatkit has saved my day more than once. In this talk, I will show you real-life examples of hard problems that I had to solve, and how Maatkit provided elegant (and most of the time very efficient) solutions.
I will cover the following short stories:
- When I run this query manually, I get an immediate answer, but when the same query is run by the application, it takes 30+s. Why?
- Did you know that the data you're backing up is not the right data?
- You say that we're running 400 SET queries/s. I doubt this, could we catch them live?
- Last time I wanted to update this field in the whole table, it took 2 weeks. Any tips to run the update faster?
- I had to skip an event on a slave. To avoid inconsistencies with the master, is rebuilding this 10GB table from scratch the only way?
- We regularly have very long queries that freeze the whole server. Could we kill them automatically if they run for more than 50s?
And a few more if time permits.
Concurrent events:
When | Event | Track | Where |
---|---|---|---|
18:00-18:45 | "KDE Abstracted My Abstraction Layer" - Multimedia Style | Crossdesktop | H.1309 |
18:00-19:00 | Booting and upgrading a flashless system | Embedded | Lameere |
18:00-19:00 | Mancoosi tools for the analysis and quality assurance of FOSS distributions | CrossDistro | H.1308 |
18:00-19:00 | Gentoo Q&A session | CrossDistro | H.1302 |
18:00-19:00 | Introduction to FreeBSD | BSD | AW1.126 |
18:15-19:00 | Open Panel Discussion | Security & hardware crypto | AW1.105 |
18:20-18:35 | chicken: Cheney-on-the-MTA | Lightning Talks | Ferrer |
18:20-18:50 | GNU recutils - your data in plain text | GNU | H.2214 |
18:30-19:00 | CloudB: a distributed hybrid storage system for the Mono framework | Mono | AW1.120 |
18:30-19:00 | Comparing Scalable NOSQL Databases: Functionality and Measurements | Data Analytics | AW1.124 |
18:30-19:00 | The latest on Gorm an GNUstep theming | World of GNUstep | AW1.117 |
18:30-19:00 | The Rise and Fall and Rise of Java | Free Java | AW1.125 |
18:40-18:55 | scala: Scala expressiveness | Lightning Talks | Ferrer |