What Should We Work On Next? Tuning Apps Without Getting Bogged Down in Maintenance
If you manage or work on a group of applications, there is constant pressure to keep their response time fast and throughput high. At the same time, your team is adding new function, changing core logic, making the apps more complex and feature-rich. How do you prioritize the tuning work that needs to be done so that your team is not bogged down in maintenance all week long? Using examples from New Relic managed applications, we will show you how to identify your best opportunities for app performance improvement by finding your slowest transaction types, slowest SQL queries, worst Solr searches, opportunities for caching and others.
- Sponsored by New Relic
Brian Doll
GitHub
Brian Doll is the Technical Marketing Manger at New Relic. He has worked with many languages and frameworks over the years in both start-up and enterprise environments. In 2007 Brian become inspired by Ruby and reinvigorated by Rails and hasn’t looked back since.
Brian lives in Marin County, California with his wife and sons where he tries to merge his passions of fitness, philosophy and programming.
















