Installation

mycache is delivered as a binary package built for your environment (PHP version, loader). We do not provide source code. WordPress/WooCommerce integration is done via the object-cache.php drop-in delivered in an encrypted version for ionCube or SourceGuardian.

What you receive
  • PHP extension: mycache.so (Linux) / the appropriate binary module for your platform
  • Encrypted drop-in: object-cache.php (ionCube or SourceGuardian)
  • Supporting files: instructions, changelog, configuration notes
  • Download access in the client panel (active license required)
Requirements
  • PHP 8.2 / 8.3 / 8.4+
  • WordPress + WooCommerce (recommended)
  • Active loader: ionCube or SourceGuardian (for the drop-in)
  • Ability to load PHP extensions (php.ini / hosting panel)
  • Available cache directory (preferred: /dev/shm or an alternative)
Deployment time

Installation typically takes a few minutes if you can edit PHP configuration. On shared hosting, you may need help from the provider.

If you are not sure which loader you have, select “I don’t know (check it)” when ordering and we’ll prepare the correct package.

Step by step

The steps below apply to most environments (VPS, dedicated servers, and many hosting panels). The main difference is how you enable the extension in PHP.

1) Download the binary package

Log in to the client panel and open Downloads. Download the package built for your environment (PHP + loader).

  • Extension: mycache.so
  • Drop-in: object-cache.php (encrypted)

2) Upload files to the server

Upload mycache.so to a location where PHP can load extensions (e.g., an extensions directory or the path required by your hosting panel).

If you use multiple PHP contexts (e.g., separate CLI and FPM), make sure you install it for the correct one.

3) Enable the mycache extension in PHP

Add the extension load directive in your PHP configuration (e.g., php.ini or a dedicated .ini file):

extension=mycache.so

After updating the configuration, restart PHP-FPM / your web server (or use the hosting panel restart option).

4) Copy the drop-in into WordPress

Copy the provided object-cache.php to:

wp-content/object-cache.php

The drop-in is delivered in an encrypted form (ionCube/SourceGuardian) and is compatible with the WordPress Object Cache API wp_cache_*.

Recommended configuration

mycache works out of the box with defaults. Below are the most commonly tuned parameters. You can set them globally in php.ini or per-request (the drop-in may set them via ini_set()).

Setting Example Description
mycache.dir /dev/shm/mycache Directory for cache files. RAM-backed (/dev/shm) is preferred, but disk is possible.
mycache.fanout 256 Number of subdirectories (power-of-two) to keep filesystem operations fast.
mycache.chmod_mode 504 (octal 0770) Directory/file permissions. Directories use SGID for group inheritance.
mycache.max_bytes 0 / 1073741824 Total cache size limit (0 = unlimited). Best-effort eviction down to ~90% of the limit.
Tip: if you host multiple sites on one server, we recommend separate cache directories per host (multi-tenant). The drop-in can do this automatically.

Loader: ionCube / SourceGuardian

The object-cache.php drop-in is encrypted and requires an active loader. This is standard practice for binary distribution and protection of integration logic.

  • If you have ionCube — download the ionCube package
  • If you have SourceGuardian — download the SourceGuardian package
  • If you are unsure — choose “I don’t know (check it)” during ordering

How to verify it works

After installation, you can confirm it in several ways:

  • In phpinfo(), you should see a mycache section with version details.
  • In WordPress: fewer SQL queries and improved TTFB (after cache warm-up).
  • In logs: no “extension not loaded” warning (otherwise the drop-in falls back to non-persistent mode).

Common issues

  • Extension does not load — wrong PHP version/architecture; download the correct build.
  • Loader error — ionCube/SourceGuardian missing or an incompatible loader version.
  • Permission denied — adjust mycache.dir and chmod_mode.
  • /dev/shm unavailable — set an alternative cache directory (e.g., a private directory in your account).
If needed, contact us and include your PHP version, loader type, and hosting details.

Need help with deployment?

Contact us for installation assistance, configuration tuning, or help choosing the correct binary package for your environment.

Contact View plans