You can point several Joomla installations at the same Memcached endpoint, but you should not assume Joomla keeps each site’s keys separate. The safest design is one Memcached instance per site, even when all instances run on the same machine. Give each instance its own port or Unix socket, then configure every Joomla site with the handler that matches its installed PHP extension. Use one shared instance only after verifying, in the exact Joomla version you run, that cache keys are namespaced per site.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What “one Memcached server” can mean
There are two different arrangements that are often described as a single Memcached server:
As an Amazon Associate I earn from qualifying purchases.
- One shared Memcached instance: every Joomla site connects to the same host and port and writes into the same key space.
- Several isolated instances on one machine: each site has its own Memcached process, port, or Unix socket, although the processes share the same physical server.
For Joomla, the second arrangement is the conservative default. The available Joomla-specific material does not establish that Joomla 4 or Joomla 5 automatically adds a unique per-site prefix to Memcached keys. Without that verification, two sites could write the same key, read another site’s cached value, or clear one another’s cache.
| Design | Isolation | Operational effect | When to use |
|---|---|---|---|
| Separate instance, port, or socket per site | Strongest practical separation | A restart or flush for one site’s cache does not target the other site’s instance | Recommended default for production sites |
| One shared instance with a verified Joomla namespace | Depends on the exact Joomla release and configuration | Uses one pool, but a flush still has a wider blast radius if the instance is shared | Only after source-level or controlled testing confirms isolation |
| One shared instance without verified namespacing | Collision risk | Sites can overwrite keys or invalidate each other’s cached data | Avoid |
Before changing Joomla
Collect the following information for every installation:
#1 Best Overall
- A-Tech RAM Memory compatible for select DDR4 Server and Workstation systems only; (*WILL NOT WORK with Desktop or Laptop Computers/PCs*)
- 32GB RAM Kit (2 x 16GB Modules); DDR4 DIMM 288 Pin; Speeds up to 2400MHz PC4-19200 (PC4-2400T)
- ECC Unbuffered UDIMM; 2Rx8 - Dual Rank x8; JEDEC DDR4 standard 1.2V
- Improves system performance, workload capacity, and reduces bottlenecks by increasing memory (RAM) resources
- Note: This memory is ECC Unbuffered and cannot be mixed with different ECC types such as ECC Registered, ECC Load Reduced, or Non-ECC Unbuffered; (Memory compatibility can vary among different system models and their installed components; please verify compatibility and follow memory channel guidelines to ensure maximum performance)
- The exact Joomla major and minor version.
- The PHP version and the installed extension class:
MemcachedorMemcache. - Whether the host exposes Memcached over TCP, a Unix socket, or both.
- The host and port (or socket path) assigned to that site’s instance.
- A backup of
configuration.phpand a maintenance window in case cached data or sessions need to be rebuilt.
Handler names are not interchangeable. The memcached handler requires the PHP Memcached class, while the memcache handler requires the PHP Memcache class. A handler that does not match the installed extension can produce a “not supported on this platform” error. Confirm the extension before selecting the handler in Joomla.
Check which PHP extension is available
Use the hosting control panel or PHP information page
Look for an enabled extension named memcached or memcache. The names are similar but represent different PHP APIs. If your provider offers a PHP module selector, record the exact module name and the PHP version to which it applies.
Check from the command line
On a server where the command-line PHP binary uses the same configuration as the web process, these checks show which class is available:
php -r "var_dump(class_exists('Memcached')); var_dump(class_exists('Memcache'));"A result of true for Memcached points to the memcached Joomla handler; a result of true for Memcache points to memcache. If the command-line result differs from the web server’s PHP information, test the web runtime as well; Joomla uses the PHP environment serving the site, not necessarily the CLI environment.
Rank #2
- OWC 32GB UPGRADE: Consists of 2pcs of 16GB DDR4 2666MHz PC4-21300 CL19 2RX8 ECC SO-DIMM 1.2V 260-pin Memory Modules Compatible with Synology part numbers D4ECSO-2666-16G, D4ES01-16G
- Compatible for Synology NAS DiskStation, RackStation, FlashStation, & NVR DVA Servers models: DS1522+, DS1618+, DS1621+, DS1621xs+, DS1819+, DS1821+, DS2419+, DS2419+II, DS2422+, DS3018xs, DS3617xs, DS3617xsII, DS3622xs+, DVA3219, DVA3221, FS1018, RS1221+, RS1221RP+, RS822+, RS822RP+
- INCREASED PERFORMANCE: Memory Upgrades are the Most Effective and Easy Way to Boost the Performance of Your Server, Micro Server or NAS System
- INDUSTRY LEADING: Consumer Friendly Advanced Replacement Program and Limited Lifetime Warranty, which Includes Free Tech Support by Other World Computing
- EASY INSTALLATION: In Most Cases Installing Memory is an Easy DIY project. Watch our OWC Basic Installation Video for help.
Do not guess from the service name
The daemon being called “Memcached” does not determine the Joomla handler. The handler follows the PHP client extension installed for that Joomla site.
Configure an isolated Memcached instance for each Joomla site
1. Allocate a distinct endpoint
Run a separate Memcached instance for each site, assigning a different unused TCP port or a different Unix socket. Keep the instances bound to an address reachable only by the web server unless remote access is explicitly required. A Unix socket can reduce network exposure, but the web-server user must have permission to open it.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →If you are on managed hosting, ask the provider whether separate instances are supported and which endpoint format they expect. Some hosting documentation uses a Unix socket path as the host value on higher-tier accounts, while stating that Memcached is unavailable on its non-Turbo shared accounts. That policy is provider-specific and should not be generalized to every host.
2. Back up the Joomla configuration
Copy each site’s configuration.php before editing it. Make the backup outside the public document root and preserve its permissions. A syntax error in this file can prevent Joomla from loading.
Rank #3
- Capacity – 32GB RAM KIT (2 x 16GB Modules) Speed up to 2400MHz Non-ECC Unbuffered 288-Pin 1.2V UDIMM.
- Specs – Black PCB Color and Dual Rank (2Rx8).
- Compatibility – Designed for selected DDR4 Desktop PCs and workstations that support 288-Pin UDIMM memory. NOT compatible with Laptop SODIMM slots.
- Installation – Plug-and-Play Upgrade, Quick and Easy to Install, no expertise required (please refer to your system's manual for guidelines).
- Warranty – All Timetec products are high-quality and rigorously tested to meet stringent standards. Backed by Timetec Limited Lifetime Warranty and professional technical support based in the United States.
3. Set Joomla’s cache options
Community configuration examples for older Joomla releases use the following properties:
public $caching = '2';
public $cache_handler = 'memcached';
public $memcached_server_host = '127.0.0.1';
public $memcached_server_port = '11211';The value 11211 is the conventional port shown in those examples. Replace the host and port with the endpoint assigned to this site. If the PHP Memcache class, rather than Memcached, is installed, use:
Recommended Free Tools
public $caching = '2';
public $cache_handler = 'memcache';
public $memcached_server_host = '127.0.0.1';
public $memcached_server_port = '11211';The property names above come from community guides for older Joomla versions. Joomla releases can change configuration details, so compare them with the configuration.php-dist file and administrator options shipped with your installed release before saving. Do not paste an older example unchanged into Joomla 4 or 5 without that check.
4. Repeat with a different endpoint for every site
Site A can use the first instance, while Site B uses another unused port or socket. The host value can remain 127.0.0.1 when both instances are local; the endpoint must still be different. Keep a written map of site, instance, host, port or socket, PHP handler, and memory allocation so that maintenance on one site does not target another.
Rank #4
- A-Tech RAM Memory compatible for select DDR4 Servers & Workstation systems only; (*WILL NOT WORK with Desktop Computers, Laptop Computers, or PCs of any kind*)
- 128GB RAM Kit (8 x 16GB Modules); DDR4 DIMM 288 Pin; Speeds up to 2133MHz PC4-17000 (PC4-2133P)
- ECC Registered RDIMM; 2Rx4 - Dual Rank x4; JEDEC DDR4 standard 1.2V
- Improves system performance, workload capacity, and reduces bottlenecks by increasing memory (RAM) resources
- Note: This memory is ECC Registered and cannot be mixed with different ECC types such as ECC Unbuffered, ECC Load Reduced, or Non-ECC Unbuffered; (Memory compatibility can vary among different system models and their installed components; please verify compatibility and follow memory channel guidelines to ensure maximum performance)
5. Clear Joomla’s existing cache after the change
Changing the backend does not convert entries already stored in the old backend. Clear the Joomla cache through the administrator interface after saving the configuration, then load the front end and administrator pages while watching the PHP and web-server logs for connection or handler errors.
If you insist on one shared instance
A single endpoint is technically simple: every site’s configuration uses the same host, port, and handler. The difficult question is isolation. The available Joomla material does not document a guaranteed per-site key prefix for current Joomla 4 or 5 releases. A setting such as $secret or $cache_platformprefix appears in one configuration guide, but that guide does not explain how either value enters the cache-key hash, and its Joomla version is not stated. Do not treat either setting as proof that sites are isolated.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Verify the exact Joomla build before sharing
- Record the complete Joomla version and the cache handler in use.
- Inspect that release’s cache classes and its
configuration.php-distin the official Joomla source repository for documented key construction or a site-specific prefix. - Install two test sites against the same Memcached instance, using different database content and unmistakably different page output.
- Warm both sites’ caches, then request the same URL patterns on each site repeatedly. Confirm that neither site displays the other’s output.
- Change a cacheable value on only one site, clear only that site’s Joomla cache, and confirm that the other site’s cached response remains unchanged.
- Repeat the test after a PHP restart and after a Memcached restart. Record the result for the exact Joomla and PHP versions that will run in production.
A successful test is evidence for that tested build and configuration; it is not a permanent Joomla-wide guarantee. Re-run it after Joomla, PHP, the cache extension, or the hosting image changes.
Understand the flush risk
With one shared instance, a flush operation acts on the instance’s keys, not on a Joomla domain name. Guidance for other systems warns that a flush can remove entries for every website connected to that instance. That is an analogy, not a Joomla-specific promise, but it is enough reason to treat shared-instance maintenance as a multi-site event. Schedule flushes deliberately and keep a recovery plan for every connected site.
Best Value
- Disclaimer: Maximum Speed requires overclocking/PC BIOS adjustments. Maximum speed and performance depend on system components, including motherboard and CPU
- Hand-sorted memory chips ensure high performance with generous overclocking headroom
- VENGEANCE LPX is optimized for wide compatibility with the latest Intel and AMD DDR4 motherboards
- A low-profile height of just 34mm ensures that VENGEANCE LPX even fits in most small-form-factor builds
- A solid aluminum heatspreader efficiently dissipates heat from each module so that they consistently run at high clock speeds
Do not invent a prefix in an unsupported setting
Adding an arbitrary configuration property does not make Joomla use it. If the installed Joomla cache class has no documented prefix option, the reliable choices are source verification, a controlled collision test, or separate instances.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Sessions are a separate decision
Page caching and session storage are not automatically the same setting. A 2014-era community forum discussion describes changing a very old Joomla installation’s session handler to memcache and adding a memcache_settings option. That procedure is not verified for Joomla 4 or Joomla 5.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Do not copy that legacy session configuration into a current site unless the installed Joomla version documents it. First determine which session handlers the administrator interface and your release’s configuration template support. If multiple sites share a session backend without proven namespacing, a collision could affect logins or session data even when page-cache tests appear clean. Keep sessions on each site’s documented backend until compatibility and isolation are confirmed.
Hosting and permissions checks
Shared hosting
Memcached availability can depend on the account tier. One hosting guide says its non-Turbo shared accounts do not support Memcached and that Turbo accounts use a Unix socket path in the host setting. Because the provider and scope of that statement are not fully established, verify support, socket path, process ownership, and connection limits with your own host.
Unix socket access
When a socket path is supplied as the host value, the PHP worker must be able to read and write to that socket. A permission failure can look like a Joomla cache failure even though the daemon is running. Check the socket’s owner, group, mode, and the user used by PHP-FPM or the web server.
Local versus remote endpoints
For a local TCP listener, 127.0.0.1 limits access to the same machine. A remote host value introduces firewall, routing, and authentication considerations that are outside Joomla’s configuration file. Restrict the Memcached listener to trusted hosts and avoid exposing it directly to the public internet.
Roll out several sites without cross-site surprises
- Inventory: list every Joomla version, PHP version, extension class, current cache handler, and existing endpoint.
- Design: assign one instance, port, or socket to each site. Reserve the shared endpoint only for a build that has passed namespace verification.
- Stage: test one non-production copy with the same PHP modules and web-server user as production.
- Back up: save each
configuration.phpand document the previous cache settings. - Configure: set
cachingto'2', choosememcachedormemcacheto match the PHP class, and enter the assigned host and port. - Warm and observe: clear Joomla’s cache, browse representative pages, and watch logs for unsupported-handler, connection, timeout, or permission errors.
- Test isolation: alter cacheable content on one site, clear that site’s cache, and confirm the other sites retain their own output.
- Document recovery: record which instance belongs to which site and which restart or flush procedure affects it.
- Repeat gradually: move the next site only after the previous site’s front end, administrator area, and login flow behave normally.
Troubleshooting by symptom
| Symptom | Likely cause | Action |
|---|---|---|
| “Not supported on this platform” | The Joomla handler does not match the installed PHP extension | Check for Memcached versus Memcache, then select the matching handler and restart or reload the PHP runtime if the extension was newly enabled |
| Joomla loads but pages remain uncached | Caching is not enabled, the endpoint is wrong, or the daemon is unreachable | Confirm public $caching = '2';, verify host and port or socket, and inspect PHP/web logs |
| One site’s content appears on another | Shared key space without reliable per-site namespacing | Disconnect the sites from the shared instance, clear affected caches, and move each site to its own instance or verified namespace |
| All sites lose cached pages after maintenance | A flush or restart targeted the shared instance | Rewarm each site’s cache and isolate instances to limit future maintenance impact |
| Unix-socket connection failure | Incorrect socket path or insufficient PHP-worker permissions | Confirm the provider’s exact path and grant access to the PHP-FPM or web-server user |
| Login or session anomalies after a cache change | Legacy or unsupported Memcached session settings | Restore the documented session handler for the Joomla release and treat page caching and sessions as separate migrations |
Practical decision rule
Use separate Memcached instances when you need a dependable production boundary, when sites have different owners, or when you cannot inspect the exact Joomla cache implementation. A shared instance is reasonable only when you have verified key namespacing for the exact release, tested collisions and flush behavior, and accepted that one maintenance action can still affect every connected site. If any of those conditions is missing, separate ports or sockets on the same physical server provide the simpler and safer answer.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
