Optimizing Django deployments with a Continuous Observability Strategy
summary
Shows a concrete stack: Blackfire.io for profiling plus Platform.sh as the deploy target, wired into CI so every push gets an isolated environment on Platform.sh. Demonstrates finding real defects like a thumbnail being generated 10,000 times and N+1s called 200 times turned into 1, measures memory and network impact, and enforces a performance budget YAML in CI so builds fail when assertions (time to first byte, query count, memory) exceed limits.
AI-written summary · about
related talks
43mOptimizing Django deployments with a Continuous Observability Strategy
01h 12mPitfalls of Continuous Deployment
34mGuide to Continuous Deployment with Rails
34mContinuous Deployment for webapps based on Django
36mContinuous Deployment with Rails
34mDeploying Without Crying: Deployment Strategies for Peaceful Nights
21mHigh-Availability Django
01h 12mPitfalls of Continuous Deployment