Your new database query ran quickly when you tested it, but seconds after deploying it, alarms are blaring, and you’re scrambling to rollback before the site goes down. What happened? I can “EXPLAIN.” Queries that perform well under development load with limited datasets can easily bring a database to its knees under production load. In this talk, you will learn to decipher query execution plans, recognize portions that can be improved, and take the necessary steps to optimize your queries!


Comments are closed.

Dave Stokes at 11:47 on 24 May 2017

One addition to the 'Christopher Simon' example. One the record with Christopher is found, the server keeps searching all the reaming records just in case there is a second record. Some folks do not understand a full table scan does read the entire table/file and does not stop after first match.

other than than minor criticism, it was you typical perfect presentation!

Karl Hepler at 12:22 on 24 May 2017

Very informative. Thank you.

Excellent talk, no suggestions because it was clear and explained the topic well.

Yar at 18:45 on 24 May 2017

Only thing that could have made it better would have been more time to run the query examples with you! This deserves a bigger time slot.

One of the best sessions I've ever attended! Explanations for all pieces were explained for beginners and refreshed for those who were already aware. I doubt that anyone left not learning something which can be difficult to do in a session that runs the gamut of expertise in a subject.

John Congdon at 09:31 on 25 May 2017

Decent talk, I was just hoping for more beyond the EXPLAIN command. I did learn a coupe of things, but not really what I expected. I should have taken the hint from the "EXPLAIN" in the text, but I think I assumed that you were going past that.

As for speaking, I would like to hear a little more range. I am guilty of this myself, so please don't take it as a harsh criticism.