Bottleneck Analysis
summary
Full-stack checklist for finding real bottlenecks: measure browser timing with Boomerang and Chrome DevTools — example: php.net shows 206ms connection, 200ms server wait and 1.2s HTML download (~2s total); test server with ApacheBench (zero failed requests, check percentiles), static vs PHP extension to reveal missing opcode cache, and large-page kernel buffer tuning for pages >50KB. Profile PHP with XHProf using auto_prepend/append and sampling, watch memcached stats (get-miss >10% or evictions >10% bad), and log slow SQL (set threshold ~1s).
AI-written summary · about
chapters (12)
- 0:00Start
- 0:52What Causes Bottlenecks?
- 14:52Initializing Boomerang
- 19:25Using Apache Bench
- 19:43Understanding Output
- 22:12Static Tests
- 26:17Network 10
- 28:26Scripting Language Overhead
- 29:34SSL Overhead
- 31:34Compression Overhead
- 38:34Profiling can cause a Bottleneck
- 45:03Memcached Stats
related talks
50m"Bottleneck Analysis"
39mPHP Performance Demystified - Measure, Understand, Optimise
55mI Feel the Need for Web Page Speed
31mNo more slow requests
50mPerformance optimization: how do I go about it?
45mPHP's biggest bottleneck, MySQL
52mUsing Blackfire to Profile Your Loading Time
27mGetting Started with Profiling Laravel Code