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:
- Simon Brown's Software Architecture for Developers Workshop (in London on 22nd - 23rd May 2017)
- Alberto Brandolini's DDD Modelling Workshop (in London on 26th - 28th June 2017)
- µCon 2017: The Microservices Conference (in London on 6th - 7th November 2017)
- Serverless Architecture with Azure Functions with Christos Matskas! (in London on 29th 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.