I really wish this went into more detail. You are notified when a query is slow. You can EXPLAIN it in chat so everybody can see. What happens next? Are slow queries treated as high priority? Is there any tooling around debugging complex queries? Basically, what makes GitHub's process different to the decades-old "grep the slow query log and run an EXPLAIN"?
How We Work on Queries at GitHub
11–20 of 30 posts
Re: How We Work on Queries at GitHub
#12Nice read Sam, thanks for the writeup.
Thought I'd let you know you have an error in your json - section.name (http://i.imgur.com/CoHol0f.png)
;]
Re: How We Work on Queries at GitHub
#13Nice read Sam, thanks for the writeup. Thought I'd let you know you have an error in your json - section.name ( http://i.imgur.com/CoHol0f.png ) ;]
haha thank you :)
Re: How We Work on Queries at GitHub
#14Is haystack open sourced anywhere?
Re: How We Work on Queries at GitHub
#15Is haystack open sourced anywhere?
Unfortunately not. It is so closely tied to our applications.
Re: How We Work on Queries at GitHub
#16Are all github internal services a dark colour scheme? good way of determining internal vs external I suppose
Re: How We Work on Queries at GitHub
#17Are all github internal services a dark colour scheme? good way of determining internal vs external I suppose
There's no hard rules on it. When I started working on it a couple of years ago, I was fond of dark color schemes for monitoring interfaces.
Re: How We Work on Queries at GitHub
#18Why doesn't Github open source their products/libraries regularly ? There is too few open source projects from Github on Github.
Re: How We Work on Queries at GitHub
#19Why doesn't Github open source their products/libraries regularly ? There is too few open source projects from Github on Github.
We do!
https://github.com/github https://github.com/libgit2 https://github.com/boxen
When it's easy to extract, well-documented, and has a clear team of maintainers, we try to open source. Sometimes it's difficult to nail one or all of those bullet points, though.
Re: How We Work on Queries at GitHub
#20Is haystack open sourced anywhere?
Unfortunately not. It is so closely tied to our applications.
Thanks for posting this! I like hearing about internal tooling. Is there more on the query tagging? How do you guys bubble query annotations through the stack?
I don't know if you're at liberty to discuss further, but how has it been scaling a giant Rails app? Have there been any pushes to break it up into smaller components? Ie. fast moving stuff stays Rails, core infra moves to something statically typed?