what should we work on next? - assets.en.oreilly.comassets.en.oreilly.com/1/event/40/what should we...
Post on 31-Jul-2020
1 Views
Preview:
TRANSCRIPT
What should we work on
Tuning apps without getting
in maintenancebogged down
next?
NewRelic.com
Brian Doll
Development > Architecture > Management > .
App Performance Engineer @ New Relic
@BrianDoll
*
NewRelic.com
RPM
NewRelic.com
RPM is Awesome
NewRelic.com
Proactive vs. Reactive
NewRelic.com
Whatshouldwe work on
next?
NewRelic.com
What is yourperspective?
NewRelic.com
Performance is Value
NewRelic.com
MaintainValue
NewRelic.com
Apdex =Satisfied Count +
Tolerating Count2
Total Samples
NewRelic.com
Break it down
NewRelic.com
(Max) Headroom?
NewRelic.com
“premature optimizationis the rootof all evil”
NewRelic.com
Optimizefor
Real World Use
NewRelic.com
DB TransactionsThe penalty box:
NewRelic.com
Web Transactions
NewRelic.com
NewRelic.com
NewRelic.com
NewRelic.com
Database Report
NewRelic.com
Every bottleneck wins!
NewRelic.comBuild Value
NewRelic.comNo roadmap
NewRelic.com
Simplicity
Communication
Feedback
Respect
Courage
NewRelic.com
Reckless Prudent
DeliberateInadvertent
“We don’t have time for design”
“We must ship now and deal with
consequences”
“What’s Layering?”
“Now we know how we should have done it”
Martin Fowler’sTechnical Debt Quadrant
NewRelic.com
A/B testing
NewRelic.com
Notes to rememberNotes to forget
NewRelic.com
Custom Dashboards
Come check us out in the exhibit hall
Wanna Race?
top related