In our SaaS, Redis is used for: bullmq job queue campaign stats compliance counters rate limiting While testing upstash redis, I found that sending just 4,000 emails triggered 150k+ redis commands. Most of it came from bullmq’s internal redis operations. At first I thought infra was expensive. Turns out, observability showed areas of improvements in our architecture. Bullmq Internals Cmd: EVALSHA Source: BullMQ Lua scripts Cmd: BRPOPLPUSH Source: Worker idle polling Cmd: DEL Source: removeOnComplete: true + lock cleanup Cmd: HEXISTS Source: BullMQ job state checks Cmd: EXISTS Source: Queue/key existence guards Is this normal considering bullmq internals workflow? Has anybody faced the same? submitted by /u/nightswordblade [link] [comments]