Common wisdom says you should not optimise or performance tune a system until you need to. This seems like very sound advice. However this little bit of advice is missing something really important. How do you know when you need to optimise?
All too often this is when a system is in production and not coping with customer load. If we are lucky major issues might be discovered during user testing right before launch. In either case we look bad in front of customers and those paying the bills.
This talk explores when to start performance testing, how to avoid the common pitfalls, how to profile when the results cause your team to pull a funny face, and what you can do about that funny face. Specific issues to Java and managed runtimes in general will be explored, but if other languages are your poison, don't be put off as much of the content can be applied to any development.
YOU MAY ALSO LIKE:
- SpringSource's What's New in Spring (in London on 16th - 18th September 2015)
- Conway's Law & Reverse Conway's Law - How to avoid being caught by it and how to turn it to your advantage (in London on 23rd September 2015)
- Whole Team Approach to Agile Testing (in London on 5th - 7th October 2015)
- µCon 2015: The Microservices Conference (in London on 9th - 10th November 2015)
Performance Testing Java Applications
Martin is a high-performance and low-latency specialist, with over two decades working with large scale transactional and big-data systems, in the automotive, gaming, financial, mobile, and content management domains.