From 207ca7271aa26ce0f65b1407dd72f39f967820e4 Mon Sep 17 00:00:00 2001 From: bazz2 Date: Fri, 26 Sep 2014 07:47:04 +0800 Subject: [PATCH] [bazz2 -ing] --- sources/talk/20140904 Making MySQL Better at GitHub.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sources/talk/20140904 Making MySQL Better at GitHub.md b/sources/talk/20140904 Making MySQL Better at GitHub.md index 1faf5d6e27..30f144c0e7 100644 --- a/sources/talk/20140904 Making MySQL Better at GitHub.md +++ b/sources/talk/20140904 Making MySQL Better at GitHub.md @@ -1,3 +1,4 @@ +[bazz2 bazz2 bazz2] Making MySQL Better at GitHub ================================================================================ > At GitHub we say, "it's not fully shipped until it's fast." We've talked before about some of the ways we keep our [frontend experience speedy][1], but that's only part of the story. Our MySQL database infrastructure dramatically affects the performance of GitHub.com. Here's a look at how our infrastructure team seamlessly conducted a major MySQL improvement last August and made GitHub even faster. @@ -89,4 +90,4 @@ via: https://github.com/blog/1880-making-mysql-better-at-github [a]:https://github.com/samlambert [1]:https://github.com/blog/1756-optimizing-large-selector-sets [2]:https://help.github.com/articles/writing-on-github#task-lists -[3]:https://github.com/blog/1603-site-maintenance-august-31st-2013 \ No newline at end of file +[3]:https://github.com/blog/1603-site-maintenance-august-31st-2013