FastPixel – Object Cache

Object Cache keeps frequently used data ready in memory, so your site serves repeat requests faster, reduces database and network overhead, and feels snappier for visitors.

Object Cache is supported in FastPixel. You can add your Redis or Memcached connection details in FastPixel > Object Cache, and the plugin will connect and use the object caching service provided by your hosting provider.

Please make sure the Redis or Memcached PHP extension is enabled on your server, otherwise the object cache feature cannot be used.

Redis DB ID (Redis only) #

Specifies which Redis database index should be used to store cached data.

Redis supports multiple logical databases inside the same Redis instance, each identified by a numeric ID (usually 0–15 by default). This option allows the cache to be isolated from other applications using the same Redis server.

Example:
If your hosting provider recommends using database 1, the plugin will store all cached objects in Redis DB 1 instead of the default 0.

Default Object Lifetime (seconds) #

Defines how long cached objects remain in the cache before they expire automatically.

Example

• 3600 → objects expire after 1 hour
• 86400 → objects expire after 1 day

Why this matters

• Lower values keep the cache fresher but may reduce cache efficiency
• Higher values improve performance but cached data may remain longer

Global Groups (one per line) #

Lists cache groups that should be treated as global across all sites in a multisite network.

Normally, object cache keys are separated per site in a multisite installation. Global groups allow certain cached data to be shared across all sites in the network.

Each group should be entered on a separate line.

Why this matters

• Prevents duplication of shared network data
• Improves performance in multisite environments

Do Not Cache Groups (one per line) #

Defines cache groups that should never be stored in the object cache.

Any objects belonging to these groups will bypass the object cache and be retrieved directly from the database.

Each group should be listed on a separate line.

Why this matters

• Avoids caching data that changes constantly
• Prevents issues with sensitive or highly dynamic information

Use persistent connections #

Keeps the connection to the Redis or Memcached server open between requests, instead of opening a new connection each time.

Persistent connections reduce the overhead of repeatedly establishing connections to the cache server.

Cache WP-Admin operations #

Allows object caching to be used inside the WordPress admin dashboard.

By default, some caching setups avoid caching admin operations to prevent issues with dynamic or user-specific data.

Store transients in object cache #

Stores WordPress transients in the object cache instead of the database.

Transients are temporary pieces of cached data used by WordPress and plugins.

Normally they are stored in the wp_options table, but when object caching is enabled they can be stored in Redis or Memcached instead.