Install Memcached from your VPS distribution, keep it bound to a private address, install a PHP client in the same runtime used by MediaWiki, and point LocalSettings.php at it with $wgMainCacheType = CACHE_MEMCACHED. On a single-server wiki, APCu may be simpler; Memcached is most useful when you need a shared object cache or expect more than one application server.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What Memcached does for MediaWiki
MediaWiki repeatedly builds objects from database rows, configuration, messages and parsed page content. An object cache stores those results in memory so later requests can reuse them instead of repeating the same work. Memcached is an optional object-cache backend; it does not replace MediaWiki’s database, file storage or PHP bytecode cache.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
MediaWiki’s performance guidance recommends a layered arrangement: “We recommend bytecode cache for PHP, APCu as local server cache, and Memcached for main cache.” APCu is local to one PHP server, while Memcached can be shared by several web or application servers. That distinction determines whether Memcached is worth the additional daemon, network and firewall configuration.
When Memcached is a good fit
- A wiki has multiple web servers that need the same object cache.
- The database is doing expensive repeated work and a shared cache can absorb it.
- You want a cache service that can be moved to a separate private node later.
- Your operations team already manages service supervision, private networking and cache monitoring.
When APCu may be better
For a small wiki with MediaWiki, PHP and the database on one VPS, APCu is often the lower-complexity choice. It avoids a network hop and a separate daemon. Memcached becomes more compelling when the cache must be shared, when the PHP workers are spread across hosts, or when you want cache capacity independent of one web server. Neither option supplies a universal speed percentage: results depend on workload, PHP opcode caching, APCu use, database latency, cache size and the number of servers.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Requirements before you install
Have all of the following ready:
- A supported Linux VPS distribution with package-manager access and shell privileges.
- A running MediaWiki installation and a way to edit its
LocalSettings.php. - PHP running through the web service that serves the wiki.
- A firewall you can configure before opening any cache traffic.
- Enough RAM for the cache without starving PHP, the database or the operating system.
Memcached is optional in MediaWiki’s installation requirements. Package names vary by distribution and release, so identify the daemon package and the PHP client package that match the PHP version used by the web service. Network communication also requires PHP sockets support.
Check the PHP runtime, not only the command-line binary
Run php -v and php -m as an initial check, but remember that the command-line PHP binary and the PHP-FPM or Apache runtime can use different versions and configuration files. The extension must be visible to the runtime that handles wiki requests. After installation, verify through the web runtime as well as the shell; a module shown by CLI PHP does not prove that MediaWiki can load it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Install the daemon and PHP client
Debian or Ubuntu package pattern
Update package metadata and install the distribution’s Memcached daemon plus the PHP client package:
sudo apt update
sudo apt install memcached php-memcachedSome releases provide versioned PHP packages instead of the generic name. Choose the package matching the PHP version used by your web service. If you choose MediaWiki’s pure-PHP client rather than the PECL extension, install the client using the method documented for your MediaWiki release and still ensure PHP sockets support is available.
After enabling a new PHP extension, restart the relevant web service so its workers load it. Restart PHP-FPM, Apache or the service that actually executes MediaWiki; restarting only the CLI shell changes nothing for existing web workers.
Choose the PHP client deliberately
MediaWiki supports a pure-PHP Memcached client and the PECL memcached extension. The PECL client can provide SASL authorization and connection pooling, although network isolation and firewall rules remain mandatory because the Memcached protocol itself has no built-in authentication. Whichever client you use, install and enable it for the web runtime, then test that runtime before changing cache settings.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Run Memcached only on a private address
For a same-VPS wiki, loopback is the safe default. MediaWiki’s example starts a daemon on loopback port 11211 with a 64 MB limit:
memcached -d -l 127.0.0.1 -p 11211 -m 64The 64 MB value is an example, not a capacity recommendation. Select a limit that fits the host after accounting for the database, PHP workers, uploads and operating-system needs. Do not replace 127.0.0.1 with a public address simply to make a remote connection work.
Make the service persistent
- Use your distribution’s Memcached service definition or service manager rather than relying on a one-time daemon command.
- Enable the service at boot and start it now.
- Inspect the service configuration and confirm its bind address, port and memory limit.
- Confirm that the listener is present only on the intended private interface.
The exact service-file layout differs between distributions and releases. Preserve the package’s supervision model, and change only the bind, port and memory settings you have consciously selected.
Confirm the listener
On the VPS, inspect listening sockets with your system’s socket tool, for example:
sudo ss -ltnup | grep 11211The output should show the address you intended, such as 127.0.0.1:11211 for a same-host deployment. If it shows a public interface, stop and correct the service configuration before putting the cache into production.
Configure MediaWiki’s main cache
Edit LocalSettings.php and add the cache settings after MediaWiki’s generated settings:
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
$wgMainCacheType = CACHE_MEMCACHED;
$wgMemCachedServers = [ '127.0.0.1:11211' ];The server entry combines the host address and Memcached port. Keep the loopback address when the daemon is on the same VPS. Save the file, check its PHP syntax if your deployment process includes a syntax check, and load the wiki before making optional cache changes.
Optional parser and message caches
MediaWiki’s documentation also shows these optional settings:
$wgParserCacheType = CACHE_MEMCACHED;
$wgMessageCacheType = CACHE_MEMCACHED;Enable them only after the main object cache works and you understand the memory available to the daemon. They increase the amount of data competing for the same cache capacity. A cache miss should be recoverable by rebuilding the value; a full cache should not take memory away from critical services.
Session settings require a version check
Session-related configuration is version-sensitive. The old $wgSessionsInObjectCache setting was removed in MediaWiki 1.33 and later, so do not copy session examples from an older installation guide. Check the configuration reference for the exact MediaWiki release before enabling any session caching. Treat session storage as a separate risk decision: losing or evicting session data can interrupt logins and edits even when ordinary object-cache misses are harmless.
Configure a separate cache node or several servers
If Memcached runs on another private host, replace the loopback address with that host’s private network address. Permit connections only from the MediaWiki application hosts. Never expose the cache port to the public internet.
Several cache servers are represented by additional entries in $wgMemCachedServers. MediaWiki also supports weighted entries for environments where cache nodes have different memory capacities. Use the syntax documented for your installed MediaWiki version rather than copying an example from an unrelated release. Unix sockets are supported with the documented unix:///path form; newer MediaWiki versions have specific rules about whether a trailing port may be included, so verify that detail against the release configuration reference.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
A multi-node layout should answer three operational questions before deployment:
- Which private addresses can initiate Memcached traffic?
- What happens to requests if one cache node is unavailable?
- Can every node resolve the hostnames consistently?
If sessions are stored in Memcached and users intermittently receive session-loss errors, MediaWiki advises checking hostname mappings on each Memcached server. Inconsistent name resolution can make a client reach a different node than expected.
Firewall and security checklist
Memcached has no security or authentication. MediaWiki’s warning is direct: “Please ensure that your server is appropriately firewalled, and that the port(s) used for memcached servers are not publicly accessible.” Apply that rule before testing from another machine.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Bind a same-VPS daemon to
127.0.0.1. - For a multi-node deployment, bind it to a private interface, not a public one.
- Block inbound TCP and UDP access from the public internet.
- Allow the Memcached port only from the MediaWiki web or application hosts.
- Do not place credentials, private tokens or other sensitive values in a cache that could be reached by an untrusted host.
- Review cloud-provider security groups as well as the VPS firewall; either layer can accidentally publish the port.
If SELinux is enabled and Apache cannot reach a private Memcached service, the MediaWiki manual documents the httpd_can_network_memcache boolean. Change that policy only when the web server needs network Memcached access, and keep the daemon restricted to the intended private network.
Verify the complete path
- Check the daemon. Confirm the service is running and listening on the expected private address and port.
- Check the PHP module. Confirm that the web PHP runtime exposes the selected pure-PHP client or PECL extension, plus sockets support.
- Check network policy. Verify that local traffic works for a same-host setup, or that only the application hosts are permitted for a separate node.
- Check MediaWiki. Load the wiki and inspect its status or debug output for cache connection errors after saving
LocalSettings.php. - Check normal behavior. Log in, open several pages and perform a low-risk edit while watching for PHP, web-server or MediaWiki cache errors.
A successful page load alone does not prove that the intended client and server are being used. A wrong PHP runtime can silently leave the extension unavailable, while a daemon listening on the wrong interface can create a serious security problem even if the wiki appears functional.
Troubleshoot common failures
“Class” or extension errors in MediaWiki
Recheck the PHP version used by the web service, not just php -m in a shell. Install the matching package, enable it for that runtime and restart the relevant PHP-FPM or Apache workers. If you selected the pure-PHP client, verify that its files are installed where MediaWiki can load them and that sockets support is enabled.
Connection refused or timeout
Compare the address in $wgMemCachedServers with the daemon’s actual bind address and port. A loopback listener cannot be reached through a server’s private network address. For a remote node, check both host firewall rules and cloud security groups, then test from an allowed application host rather than from the public internet.
Recommended Free Tools
The daemon starts but is exposed publicly
Stop it, change the bind address to loopback or the private interface, restart it through the service manager and verify the listener again. Add an explicit firewall deny for public TCP and UDP access. Do not treat an obscure port as protection; Memcached has no authentication.
Intermittent session loss
If session caching is enabled, first verify that the setting is valid for your MediaWiki version. Then check that every Memcached server has consistent hostname mappings and that requests are not being sent to an unintended node. Session failures are a reason to simplify the topology until ordinary object caching is stable.
Memory pressure or little apparent benefit
Memcached is an eviction cache, not permanent storage. Reduce its limit if PHP or the database is starved, or increase capacity only when the host has safely available RAM. A small, lightly used wiki may see little improvement because APCu, opcode caching or database latency dominates its requests. Measure page and database behavior for your workload instead of promising a generic percentage gain.
APCu versus Memcached at a glance
| Decision axis | APCu | Memcached |
|---|---|---|
| Scope | Local to one server | Can be shared by multiple application servers |
| Best fit | Small, single-server wiki | Shared or distributed object cache |
| Operations | PHP extension with no separate network daemon | Separate daemon, service supervision and firewall rules |
| Network exposure | Local process memory | Requires private binding and access control when remote |
| PHP requirements | APCu extension | Pure-PHP client or PECL memcached, plus sockets for network communication |
| Failure impact | Usually a local cache miss | Object-cache misses are recoverable, but session use can cause login or edit interruptions if configured poorly |
The practical choice is architectural rather than a contest over a single benchmark. Use APCu when locality and simplicity win; use Memcached when a shared cache solves a real multi-process or multi-server problem.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRecommended deployment sequence
- Confirm that Memcached is appropriate for the wiki’s size and topology.
- Identify the PHP runtime serving MediaWiki and its compatible client package.
- Install the daemon and client, then restart the web runtime.
- Bind Memcached to loopback for a same-VPS deployment, or to a private interface for a separated deployment.
- Enable the service at boot and verify its listener.
- Apply firewall rules before allowing any remote connection.
- Set
$wgMainCacheTypeand$wgMemCachedServersinLocalSettings.php. - Test the wiki, inspect status or debug output, and watch logs.
- Add parser, message or version-appropriate session settings only after the basic cache path is reliable.
Bottom line
For MediaWiki and Memcached on one VPS, the safe baseline is simple: install the distribution packages, run Memcached on 127.0.0.1:11211, install a client visible to the web PHP runtime, and configure CACHE_MEMCACHED with $wgMemCachedServers. Keep the service private because it has no authentication. Choose APCu instead when a small single-server wiki does not need a shared cache, and treat any performance improvement as workload-dependent rather than guaranteed.
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.
