Your SlideShare is downloading. ×
What should we work on next?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

What should we work on next?

1,126
views

Published on

Using New Relic RPM proactively to build performance into your applications. RailsConf 2010

Using New Relic RPM proactively to build performance into your applications. RailsConf 2010

Published in: Technology, Business

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,126
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
38
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. What should we work on next? Tuning apps without getting bogged down in maintenance
  • 2. Brian Doll * Development > Architecture > Management > . App Performance Engineer @ New Relic @BrianDoll NewRelic.com
  • 3. RPM NewRelic.com
  • 4. RPM is Awesome NewRelic.com
  • 5. Proactive vs. Reactive NewRelic.com
  • 6. What should we work on next? NewRelic.com
  • 7. What is your perspective? NewRelic.com
  • 8. Performance is Value NewRelic.com
  • 9. Maintain Value NewRelic.com
  • 10. Tolerating Count Satisfied Count + 2 Apdex = Total Samples NewRelic.com
  • 11. Break it down NewRelic.com
  • 12. (Max) Headroom? NewRelic.com
  • 13. “premature optimization is the root of all evil” NewRelic.com
  • 14. Optimize for Real World Use NewRelic.com
  • 15. DB Transactions The penalty box: NewRelic.com
  • 16. Web Transactions NewRelic.com
  • 17. NewRelic.com
  • 18. NewRelic.com
  • 19. NewRelic.com
  • 20. Database Report NewRelic.com
  • 21. Every bottleneck wins! NewRelic.com
  • 22. Build Value NewRelic.com
  • 23. No roadmap NewRelic.com
  • 24. Simplicity Communication Feedback Respect Courage NewRelic.com
  • 25. Martin Fowler’s Technical Debt Quadrant Reckless Prudent “We don’t have “We must ship time for design” now and deal with consequences” Deliberate Inadvertent “Now we know “What’s how we should Layering?” have done it” NewRelic.com
  • 26. A/B testing NewRelic.com
  • 27. Notes to remember Notes to forget NewRelic.com
  • 28. Custom Dashboards NewRelic.com
  • 29. Wanna Race? Come check us out in the exhibit hall