$ the-wire · showcase
DJANGO PATCHES CACHE CULLING BOTTLENECK, FIXES TEST ISOLATION BUGS ACROSS SUITE
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
2 people shipped this
Django shipped a performance optimization that cuts unnecessary cache culling operations, while a wave of test isolation fixes prevents database leaks that have been causing intermittent failures in production test runs.
The headline story is the DBCache culling optimization [1], which adds a configurable option to skip culling on every query and instead batch it more intelligently. This addresses a real performance drag for teams running heavy cache workloads. In parallel, the Django test suite got serious hardening with two critical isolation fixes [2] [3] that resolve a recurring pattern: cached Site instances were triggering unexpected database writes to 'other' databases during test setup, silently breaking test isolation assumptions. These weren't random failures, they were architectural problems in how test fixtures interact with cache state. The fixes force explicit database declarations in affected test classes, preventing the kind of creeping test flakiness that tanks CI confidence. No breaking changes here, but the test isolation work is worth reading if you maintain custom test suites that inherit from Django's base test classes.
Action items
- → Review the DBCache culling config if you manage high-traffic cache layers django/django [plan]
- → Check your test suite for database isolation issues using the new patterns from refs 3 and 5 django/django [monitor]
References
- [1] Fixed #32785 -- Optimize cull frequency for DBCache. ↗ django/django
- [2] Refs #16281 -- Fixed isolation of admin_views.ViewOnSiteTests. ↗ django/django
- [3] Refs #16281 -- Fixed isolation of admin_views.ViewOnSiteTests. ↗ django/django
