memcached is a high performance multithreaded event-based key/value cache store intended to be used in a distributed system.
memcached-windows is a native Windows port of memcached without using a compatibility layer like Cygwin or Windows Subsystem for Linux. It is instead using Mingw-w64 to produce native Windows binaries. See Why native? wiki for the advantages. Released binaries are transparently built, tested, and reproducible (see https://ci.appveyor.com/project/jefty/memcached-windows).
memcached-windows is verified using the same test suite as the official memcached. All tests PASSED!
memcached-windows will be regularly merged, built, and tested with upstream/official memcached's latest releases. See wiki for more info.
| GitHub (AppVeyor CI) | Latest |
| AppVeyor CI | Artifacts |
- CI outputs and saves the final archives' hashes and can be compared with the released hashes. This is one way to confirm binaries' origin.
- Aside from the hashes, Bintray binaries are also GPG-signed. Verify with public key.
Minimum Requirement: Windows Vista/Windows Server 2008
- NOTE: -s/unix-socket requires at least Windows 10 version 1803/Windows Server 2016 version 1803 to work. Run sc query afunix to check if OS is supported. Socket creation error will occur for unsupported OS.
- Just execute memcached.exe (Options are same except the unsupported)
- Just execute memcached.exe --help for more info
- sasl (-Y/--auth-file with TLS/SSL enabled is a good alternative)
- -u/user (Better use Windows runas command, Windows explorer's Run as different user context menu, or other Windows built-in tools)
- -r/coredumps (Mingw-w64 currently doesn't support coredump but check Runtime and Crash Analysis wiki to know how to achieve same purpose using native Windows crash dumps.)
- -k/lock-memory (Windows does not currently support locking of all paged memory)
- seccomp
Feel free to use the issue tracker on github.
If you are reporting a security bug please contact a maintainer privately. We follow responsible disclosure: we handle reports privately, prepare a patch, allow notifications to vendor lists. Then we push a fix release and your bug can be posted publicly with credit in our release notes and commit history.