Blog Sections Open
Why Database Time Is Not Zero Even When Query Count Is Zero
A zero query count in parser stats does not always mean truly zero database-related overhead; some measured timings can still include framework or connection-layer work.
Developers often log parser statistics in the footer to identify slow pages. One confusing case is when [^q^] reports zero queries but [^qt^] still shows a small non-zero time.
Why that happens
Timing counters are not always as literal as they look. A page can report no tracked content queries while still incurring low-level connection, initialization, or framework-side timing overhead that lands in the DB timer bucket.
Recommendation
Treat parser stats as directional diagnostics, not as perfect forensic truth. If a tiny non-zero DB time appears with zero visible queries, that is usually normal and not a reason to panic.
Preparing MODX Evo and Revo Sites for DDoS Pressure
A CMS alone will not absorb multi-gigabit junk traffic, so DDoS resilience starts with hosting, edge protection, and request-layer strategy rather than snippet tweaks.
Keeping Test and Production Servers in Sync Safely
A test server is useful only if deployment back to production is deliberate, repeatable, and does not overwrite live data blindly every night.