Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

WordPress object caching: when Redis helps and what to measure first

Published August 2026 · 2 min read · Updated 2026-09-05

WordPress object caching stores results of repeated database/object lookups between requests when a persistent backend such as Redis is configured. It can reduce query work, but it is not a page cache and can create correctness problems if a plugin assumes data changes are instantly visible without proper cache invalidation.

Establish whether database work is the bottleneck

Measure query count/time on representative uncached PHP requests before adding Redis or another object backend. A slow external API, PHP computation, or large uncached page will not become fast because object caching exists.

Identify repetitive option, metadata, and query patterns that a persistent cache can actually reuse.

Size memory and eviction behavior

Persistent cache data consumes RAM. Choose a maxmemory policy appropriate to ephemeral cache data and monitor used memory, evictions, hit rate, connection count, and latency.

Do not place irreplaceable application state in a cache instance configured to evict keys.

Protect network and authentication

Bind Redis/cache services only where the application needs them; do not expose them openly to the internet. Use authentication/ACLs and firewall/private paths appropriate to the deployment.

If several sites share a backend, use safe key prefixes/database separation supported by the WordPress cache implementation.

Test invalidation and plugin compatibility

Change posts, options, users, products, and plugin settings and confirm updates appear promptly. Keep a documented cache flush procedure for troubleshooting without treating flush-all as the normal solution.

  • Measure DB bottleneck first.
  • Monitor memory/evictions/hit rate.
  • Keep cache private.
  • Test invalidation on real changes.

Next step

Measure database work before adding persistent object cache, then watch memory, evictions, hit rate, isolation and invalidation after Redis is enabled.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move