How can I improve Redis performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
I'm deploying a Symfony application (6.4 LTS) that currently runs on a single server using the default filesystem cache adapter defined in config/packages/cache.yaml . Read traffic is heavy and writes are infrequent, and the app performs well today. However, we're planning to scale horizontally to three nodes behind a load balancer within the next quarter, w
Weblate utilizes Celery and Redis to manage asynchronous translation tasks. During a version upgrade, the system executes Django migrations to update the PostgreSQL schema and updates the application logic to handle new task signatures. A critical boundary exists between the persistent database state and the volatile task queue in Redis. If an upgrade fails
Redis Sorted Sets (ZSETs) are frequently used for time-series indexing by storing Unix timestamps as scores. This allows for efficient range queries using ZRANGEBYSCORE . However, Redis stores scores as double-precision floating-point numbers. When implementing high-resolution telemetry, there is a concern regarding the precision limit of these floating-poin
Goal: Ensure that Shopware’s HTTP cache is fully populated before production traffic arrives, regardless of whether the filesystem or Redis adapter is used. Constraint: The default warm‑up mechanism only populates the filesystem cache; when the Redis adapter is enabled the cache remains cold until the first request, which can cause latency spikes. Additional
In Vue Storefront (Alokai), anonymous catalog pages are usually cached in layers: a server-side cache such as Redis for API and SSR aggregation, plus a CDN for anonymous traffic, while cart, checkout, and customer routes are excluded from shared caches. The unresolved point is how to render personalized header fragments—mini-cart counters, wishlist totals, o
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
Recently, we had an outage due to Redis being unable to write to a file system (not sure why it's Amazon EFS) anyway I noted that there was no actual HEALTHCHECK set up for the Docker service to make sure it is running correctly, Redis is up so I can't simply use nc -z to check if the port is open. Is there a command I can execute in the redis:6-alpine (or n
KrakenJS utilizes a plugin-based architecture where the core engine manages the request lifecycle via middleware. When integrating a Redis-backed caching plugin, the framework typically intercepts requests to serve stored responses before they reach the route handler. A specific architectural challenge arises when the internal state-tracking of the caching p