Question posted in 
As per documentation of redis,
A.3.1 Drawbacks of Redis on Windows
Windows doesn’t support the fork system call, which Redis uses in a
variety of situations to dump its database to disk. Without the
ability to fork, Redis is unable to perform some of its necessary
database-saving methods without blocking clients until the dump has
completed.
Questions:
1) If I’m not wrong, this issue will occur when concurrent users increases? Is that correct?
2) Is it really an issue, if we deploy channels on a windows machine (production server)? If yes, is there any better alternative of redis?
3) How to test the above-mentioned drawback on a production server?
Note:
Can’t use wsl2(as officially not released) or wsl as the current windows server won’t support.
2
Answers
as far as I know to come over this issue you may try one of these options:
setup redis on a docker container using this image and use it in your project.
install linux using a virtualbox and setup redis there.
In both of them since you are running redis in linux environment I don’t think you get a problem but like I said try them before going to production. 🙂
For testing purpose maybe a simulation would work fine first write a test with lots of read and write and try it on both redis on windows and redis on docker and measure the benchmarks.
Memurai is a good Redis for Windows alternative. Memurai is based on Redis source code.