Have you read a contributing guide?
Clear and concise description of the problem
Do you have any plans, or would you consider, switching to valkey instead of staying with redis? In addition to superior multithreaded performance, valkey generally is more efficient with memory. Alternatively, do you plan to stick with redis <= 7.2? I would like to use valkey instead of redis but do not want to introduce any future breaking changes.
Suggested solution
Update docker-compose.yml to use valkey/valkey-bundle:9.0.1 (the latest stable version as of 2025-12) and functionally equivalent to redis-stack-server:7.2.0 (the currently used redis in any-sync-dockercompose). If a more minimal image is desired and the extra functionality of stack-server is not needed, then valkey/valkey:9.0.1-alpine that also loads valkey-bloom module (which the documentation states is a hard requirement for filenode), although this is more complicated in docker compose unless additional valkey.conf is included in any-sync repo.
Alternative
No response
Additional context
No response
Have you read a contributing guide?
Clear and concise description of the problem
Do you have any plans, or would you consider, switching to valkey instead of staying with redis? In addition to superior multithreaded performance, valkey generally is more efficient with memory. Alternatively, do you plan to stick with redis <= 7.2? I would like to use valkey instead of redis but do not want to introduce any future breaking changes.
Suggested solution
Update docker-compose.yml to use valkey/valkey-bundle:9.0.1 (the latest stable version as of 2025-12) and functionally equivalent to redis-stack-server:7.2.0 (the currently used redis in any-sync-dockercompose). If a more minimal image is desired and the extra functionality of stack-server is not needed, then valkey/valkey:9.0.1-alpine that also loads valkey-bloom module (which the documentation states is a hard requirement for filenode), although this is more complicated in docker compose unless additional valkey.conf is included in any-sync repo.
Alternative
No response
Additional context
No response