samlambert

29 ms·

1. 331.▲
   by samlambert 12y ago

   It is certainly helpful for grabbing bits of data that you want quickly, it is also another line of defense for DR. If we make a change and want to quickly compare against an older version of the data delayed slaves are super handy. We can
2. 332.▲
   by samlambert 12y ago

   Both Xtrabackups and mysqldump for logical backups.
3. 333.▲
   by samlambert 12y ago

   Nope.
4. 334.▲
   by samlambert 12y ago

   I have tested thread pooling with our workload and it didn't go so well. Also > Note This feature implementation is considered BETA quality.
5. 335.▲
   by samlambert 12y ago

   I think all of us where at home during this. I certainly was.
6. 336.▲
   Making MySQL Better at GitHub(github.com)

   195 points by samlambert 12y ago|140 comments
7. 337.▲
   by samlambert 12y ago

   If we get a spike in slow queries we get alerted via pager etc. If a query is slow enough to be killed Hubot tells us https://twitter.com/isamlambert/status/502818333914566656 I am working on some query linting as
8. 338.▲
   by samlambert 12y ago

   I'm not sure tbh, I think it makes it easier for graphs to stand out. I do love the interface of Haystack.
9. 339.▲
   by samlambert 12y ago

   There is a little more info on query comments here: http://samlambert.com/posts/the-power-of-query-comments/
10. 340.▲
    by samlambert 12y ago

    Unfortunately not. It is so closely tied to our applications.
11. 341.▲
    by samlambert 12y ago

    haha thank you :)
12. 342.▲
    by samlambert 12y ago

    Hey! Thank you for the welcome :)
13. 343.▲
    by samlambert 12y ago

    Basically you can hit /mysql clone for any table and it will make its way to an isolated db for the user running the command. It would be cool to be able to pass the script a query and have it clone all the tables.
14. 344.▲
    How We Work on Queries at GitHub(samlambert.com)

    82 points by samlambert 12y ago|29 comments