Choose your read-cache settings.

Memory policy

Choose Consume system memory, 50%, 75%, or a custom GiB value. Automatic policies reserve operating headroom and resolve against the Accelerator host at startup. Changed policies take effect after restart.

Startup warm-up

The Accelerator forwards requests to the database while filling its cache during startup bypass. The default warm-up interval is 120 seconds. After that interval, eligible requests can use valid cached results.

Object scope

Choose schemas and objects for read caching. The scope command supports tables, views, procedures and any object type. An empty scope selects all eligible objects. Review the selected engine’s CDC and metadata permissions.

accel scope put application "*" any 1 0
accel show
accel check

Committed changes

CDC tracks committed database changes, including writes made outside the Accelerator, and maintains affected cache entries. When CDC cannot establish coherence, the Accelerator bypasses cached reads and resynchronizes.