The talker was obviously extremely knowledgable and knew how to bring the material in a very interesting way.
Unfortunately a lot of time was wasted at the start of the course on technical problems that simply could've been bypassed by using the slides. This resulted in the most interesting part of the entire talk being rushed way to hard, a bit of a letdown :-/
Hopefully the slides are released so that I can look them over at a lower pace.
Great talk, it really helped clear up some of the "why" behind optimising MySQL. Adrian was a really good speaker and clearly knew his stuff.
I can only repeat Steve's comment, its a shame that the start of the session was plagued with technical issues which ate into the time and meant the end of the talk had to be rushed.
Look forward to seeing the slides at some point to go over them again.
I really enjoyed this talk, It was a shame that through no fault of the speaker it had cut off a little early due to the technical issues with the venue at the start.
I found this tutorial really informative, and could tell that Adrian really knew his stuff, and more to the point that he really loved talking about it. I accosted him with a question or two in the bar afterwards about specific scenarios and he was only too happy to oblige me with answers.
Nice approach to the problem of having 10+ folk doing work together on your laptop, however you should have scripted that so you can cope with additional people attending. Plan for the unexpected.
As others have said time was wasted early on, leaving pregnant pauses and losing your audience, you pulled it back but left too little time to do justice to the later material.
Given I know the circumstances prior to the session, I'll simply say well done, I enjoyed it overall!
I've been EXPLAINing everything since attending, and seeing the benefits in our apps already! Some really simple and effective advice there.
One thing that wasn't mentioned was using the smallest key size possible. I've seen plenty of people designing DB's use the default INT(11) PK's where TINYINT would easily suffice.
Comments
Comments are closed.
The talker was obviously extremely knowledgable and knew how to bring the material in a very interesting way.
Unfortunately a lot of time was wasted at the start of the course on technical problems that simply could've been bypassed by using the slides. This resulted in the most interesting part of the entire talk being rushed way to hard, a bit of a letdown :-/
Hopefully the slides are released so that I can look them over at a lower pace.
Great talk, it really helped clear up some of the "why" behind optimising MySQL. Adrian was a really good speaker and clearly knew his stuff.
I can only repeat Steve's comment, its a shame that the start of the session was plagued with technical issues which ate into the time and meant the end of the talk had to be rushed.
Look forward to seeing the slides at some point to go over them again.
I really enjoyed this talk, It was a shame that through no fault of the speaker it had cut off a little early due to the technical issues with the venue at the start.
I found this tutorial really informative, and could tell that Adrian really knew his stuff, and more to the point that he really loved talking about it. I accosted him with a question or two in the bar afterwards about specific scenarios and he was only too happy to oblige me with answers.
Probably my favorite of the weekend so far.
Nice approach to the problem of having 10+ folk doing work together on your laptop, however you should have scripted that so you can cope with additional people attending. Plan for the unexpected.
As others have said time was wasted early on, leaving pregnant pauses and losing your audience, you pulled it back but left too little time to do justice to the later material.
Given I know the circumstances prior to the session, I'll simply say well done, I enjoyed it overall!
I've been EXPLAINing everything since attending, and seeing the benefits in our apps already! Some really simple and effective advice there.
One thing that wasn't mentioned was using the smallest key size possible. I've seen plenty of people designing DB's use the default INT(11) PK's where TINYINT would easily suffice.
Overall I learnt heaps, thanks!