Please log in to watch this conference skillscast.
Knuth said it first: ""97% of the time, premature optimisation is the root of all evil"". And it's become a mantra: ""You aren't going to need it - Don't worry about speed - wait until we performance test and then tweak the slow parts"". But it's not always that simple. Will you actually get around to those tests? Will you be able to understand the results? And by the time you understand them, will it be too late or too expensive to fix?
In this talk I will discuss my experiences diagnosing and fixing performance problems in real-world clojure applications, and some practical approaches to making this less painful.
YOU MAY ALSO LIKE:
- How the JVM executes Java (in London on 24th July 2017)
- Gojko Adzic's Impact Mapping Workshop (in London on 27th September 2017)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 7th - 8th November 2017)
- Agile Testing & BDD eXchange 2017 (in London on 9th - 10th November 2017)
Pragmatic Clojure Performance Testing
Korny works for ThoughtWorks as a developer, consultant and compensating optimist. He has been developing mostly in Clojure for the past 2 years, and in a range of lesser languages for a long time before that.