Redis on Windows
Redis 3.0 Branch
- This is a port for Windows based on Redis 3.0.
- There is support for the 64-bit version. We have dropped official support for the 32-bit version, though you can build it from source if desired.
- The latest unsigned binaries are available from the Release Page.
- Signed binaries can be downloaded using Nuget and Chocolatey.
- Redis on Windows uses a replacement for the UNIX fork() API that simulates the copy-on-write behavior using the system paging file.
- Because Redis makes some assumptions about the values of file descriptors, we have built a virtual file descriptor mapping layer.
- Redis on Windows can be installed as a Windows Service.
Redis 3.0 release notes
- Redis on UNIX release notes
- Redis on Windows release notes
How to configure and deploy Redis on Windows
How to build Redis using Visual Studio
You can use the free Visual Studio Community edition.
-
Open the solution file msvs\redisserver.sln in Visual Studio, select a build configuration (Debug or Release) and target (x64) then build.
This should create the following executables in the msvs$(Target)$(Configuration) folder:
- redis-server.exe
- redis-benchmark.exe
- redis-cli.exe
- redis-check-dump.exe
- redis-check-aof.exe
Unit Testing
To run the Redis test suite requires some manual work:
- The tests assume that the binaries are in the src folder. Use mklink to create a symbolic link to the files in the msvs\x64\Debug|Release folders. You will need symbolic links for src\redis-server, src\redis-benchmark, src\redis-check-aof, src\redis-check-dump, src\redis-cli, and src\redis-sentinel.
- The tests make use of TCL. This must be installed separately.
- To run the tests you need to have a Unix shell on your machine, or MinGW tools in your path. To execute the tests, run the following command: "tclsh8.5.exe tests/test_helper.tcl --clients N", where N is the number of parallel clients . If a Unix shell is not installed you may see the following error message: "couldn't execute "cat": no such file or directory".
- By default the test suite launches 16 parallel tests, but some of the tests may fail when the number of clients is greater than 2.