Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,23 @@ services:
image: valkey/valkey:8-alpine
ports:
- "6382:6379"
command: ["valkey-server", "--maxmemory", "256mb", "--maxmemory-policy", "volatile-lru", "--appendonly", "yes"]
# Aggressive cache mode: LRU, 1GB, no persist
command:
- valkey-server
- --maxmemory
- 1gb
- --maxmemory-policy
- allkeys-lru
- --save
- ""
- --appendonly
- "no"
- --tcp-backlog
- "2048"
Comment on lines +88 to +89

Copilot AI Apr 9, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--tcp-backlog 2048 may not take effect if the kernel net.core.somaxconn is lower (Valkey will cap the effective backlog). If you rely on 2048 for connection spikes, consider also setting an appropriate sysctl for the container/host so the backlog setting is actually honored.

Copilot uses AI. Check for mistakes.
- --timeout
- "0"
- --tcp-keepalive
- "60"
volumes:
- bcproxyai-redis:/data
Comment on lines +92 to 95

Copilot AI Apr 9, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--save "" and --appendonly no stop new RDB/AOF writes, but the service still mounts a persistent volume at /data. If a dump.rdb already exists in that volume, Valkey can still load it on startup, which conflicts with the “no persistence” goal. Consider removing the named volume (or switching to tmpfs: /data) and ensuring /data is empty on deploy to make the cache truly ephemeral.

Copilot uses AI. Check for mistakes.
healthcheck:
Expand Down