What is this?
This is an unofficial native port of Redis for Windows x64. Redis is an in-memory key-value database that persists on disk, and this project rebuilds it so it runs as a real Windows program.
This is an unofficial native port of Redis for Windows x64. Redis is an in-memory key-value database that persists on disk, and this project rebuilds it so it runs as a real Windows program.Is it the actual Redis server, or some kind of wrapper?It is the actual Redis server ported natively. You get the usual key-value model with Strings, Lists, Sets, Sorted Sets, Hashes, Streams and HyperLogLogs, kept in memory and persisted to disk.
It is the actual Redis server ported natively. You get the usual key-value model with Strings, Lists, Sets, Sorted Sets, Hashes, Streams and HyperLogLogs, kept in memory and persisted to disk.How do I install it on Windows?Download a prebuilt release from the releases page — Redis 5.0.14 or 4.0.14 for Windows x64, published there as MSI installers you can run directly.
Download a prebuilt release from the releases page — Redis 5.0.14 or 4.0.14 for Windows x64, published there as MSI installers you can run directly.Is this an official port from Microsoft or the Redis team?No — it is unofficial. It continues the archived win-3.2.100 port from MS Open Tech: the sources were merged by hand, projects updated to Visual Studio 2019, and findings (mostly via unit tests) were fixed.
No — it is unofficial. It continues the archived win-3.2.100 port from MS Open Tech: the sources were merged by hand, projects updated to Visual Studio 2019, and findings (mostly via unit tests) were fixed.Are there 32-bit builds too, or is it x64-only?The stable branches are Windows x64 ports — the published Redis 4.0.14 and 5.0.14 releases are built for x64.
The stable branches are Windows x64 ports — the published Redis 4.0.14 and 5.0.14 releases are built for x64.How did the author get Redis, a C project, to run natively on Windows?Beyond updating the code to Visual Studio 2019 projects, the port ships a customized jemalloc allocator: Windows VirtualAlloc/VirtualFree calls are replaced with AllocHeapBlock/PurgePages and FreeHeapBlock helpers so the port can track which memory regions are made available to child processes when saving RDB/AOF files. Those jemalloc changes are maintained in their own repository and copied into deps/jemalloc.
Beyond updating the code to Visual Studio 2019 projects, the port ships a customized jemalloc allocator: Windows VirtualAlloc/VirtualFree calls are replaced with AllocHeapBlock/PurgePages and FreeHeapBlock helpers so the port can track which memory regions are made available to child processes when saving RDB/AOF files. Those jemalloc changes are maintained in their own repository and copied into deps/jemalloc.Is it stable enough to rely on?Both the win-4.0.14 and win-5.0 branches are labeled stable ports, but the author still asks users to test the releases and report any issues, so treat it as a community-maintained port you should validate against your own workload.
Both the win-4.0.14 and win-5.0 branches are labeled stable ports, but the author still asks users to test the releases and report any issues, so treat it as a community-maintained port you should validate against your own workload.Which topics is it in?key-value-store, cache, key-value, nosql, installer, redis, windows-app, c, command-line, database, command-line-tool, free
key-value-store, cache, key-value, nosql, installer, redis, windows-app, c, command-line, database, command-line-tool, free