ERPNextCalc Redis RQ Short, Default & Long Queue Isolation
ERPNextCalc separates Redis RQ background consumers into three isolated Supervisor process groups—short (512 MB), default (768 MB), and long (1024 MB)—so slow batch jobs never block real-time webhooks.
In our audit of manufacturing benches, running a single undifferentiated worker pool causes email notifications and stock reservation queues to stall for 15+ minutes whenever a 4-level BOM explosion executes.
ERPNextCalc Queue Memory Allocation (512 MB to 1,024 MB)
Each short worker handles lightweight 30-second tasks like transactional emails or payment gateway callbacks and averages 512 MB RSS. Default workers process GL reposting at 768 MB, while long workers spike to 1,024 MB during bulk CSV imports.
We recommend running a minimum 2:2:1 ratio (2 short, 2 default, 1 long) on 16 GB nodes, reserving 3,584 MB total for asynchronous queues.
ERPNextCalc Redis Port Separation (:11000 vs :13000)
Frappe v15 requires two independent Redis instances: redis_queue on port 11000 without aggressive LRU key eviction, and redis_cache on port 13000 configured with allkeys-lru.
We advise allocating at least 512 MB maxmemory to redis_queue and disabling RDB snapshotting on redis_cache to prevent fork latency spikes.
ERPNextCalc Redis RQ Split in common_site_config.json
ERPNextCalc FAQ: What happens if redis_queue runs with allkeys-lru eviction?
Pending RQ job payloads can be silently evicted under memory pressure, causing scheduled ERPNext payroll or stock reposting jobs to vanish without logs.