Defining and Using Key Metrics to Master Performance Measurements
summary
Explains that metrics are labeled collections of function costs (wall time, CPU, I/O, memory) gathered by the Blackfire probe, shows hundreds of built‑ins and how to define custom ones in .blackfire.yml with selectors, uses PHP SDK markers that are no‑ops without a profile, demonstrates timeline markers and the metrics explorer, proves a test failing because a metric count is 23 calls when it should be zero, and shows argument‑capturing that splits nodes in the call graph.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:13What Are Metrics
- 1:10Timeline View
- 4:15Recommended Recommendations
- 5:35Built-In Metrics with Blackfire
- 8:27Define Metrics
- 10:47Selector
- 21:58The Metrics Explorer
related talks
36mMetrics - What's your code actually doing?
23mYou Get What You Measure—Why Metrics Are Important
58mSystem Metrics: Collecting the Gotchas
38mThe Metric System: Making Correct Performance Measurements
39mProfiling and Benchmarking 101
01h 01mFinding Metrics that matter and using them safely
37mYou Can't Optimize What You Can't Measure
52mUsing Blackfire to Profile Your Loading Time
