№ 32 ERPNextCalc
Frappe Gunicorn FinOps Sheet
Rate Baseline: 2026-11-12
Methodology
Deterministic Math
Unit Precision
USD (/mo • /yr)
Commercial Firewall
100% Independent
Direct Utility
Open Calculator →

ERPNextCalc affiliate disclosure (Redis RQ Short, Default & Long Queues | ERPNextCalc): outbound provider links may earn a referral commission at zero added cost. Read ERPNextCalc disclosure.

Background Worker Queues

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

{
  "redis_cache": "redis://127.0.0.1:13000",
  "redis_queue": "redis://127.0.0.1:11000",
  "background_workers": 5,
  "rq_queue_split": { "short": 2, "default": 2, "long": 1 }
}
Queue TierRAM / WorkerStopwaitsecsTypical ERPNext Jobs
short512 MB360sEmail queue, webhooks, POS sync
default768 MB600sGL reposting, workflow transitions
long1,024 MB1,800sBOM explosion, period closing, backups

Explicitly budgeting Redis RQ pools in ERPNextCalc eliminates silent background bottlenecks across warehouse and accounting workflows.

Adjust the Short, Default, and Long sliders on ERPNextCalc to recalculate total memory headroom before deploying Supervisor.

ERPNextCalc Background Worker Queues FAQ

#1 UltaHost Dedicated EPYC VDS: $37.50/mo • #2 Hostinger KVM NVMe: $10.49/mo Claim UltaHost Rate →
DIRECT ERPNEXTCALC HOSTING VERDICT — 8000 DAILY ERP VOUCHERS Target sites/common_site_config.json
RECOMMENDED HOST

UltaHost Dedicated EPYC VDS

$37.50/mo

ERPNextCalc 16GB pick (116,000 IOPS) — Dedicated VDS RAID-10 NVMe + 150Gbps DDoS

Claim 2026 Discount →
SUBSEA ROUTE PICK

Hostinger KVM NVMe

$10.49/mo

Low-RTT node for frappe-bench gunicorn (105 ms ledger post)

Start Cloud Trial →
FIXED TARIFF TIER

InterServer Price-Lock KVM & ZFS

$6.00/mo

Steady ERPNextCalc secondary tier (1500–8000 daily ERP vouchers)

Review Fixed Slice →
ERPNextCalc Partner Voucher (UltaHost): 40% Off Annual VDS + Free Managed Migration
ERPNextCalc Redis RQ Short, Default & Long Queue Isolation — ERPNextCalc NVMe VPS sizing and latency benchmark diagram
Chart 1: tabGL Entry & tabStock Ledger Entry InnoDB pages throughput (116,000 IOPS) for ERPNextCalc nodes.
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.

frappe-bench gunicorn + python-rq + MariaDB Host Selection — IOPS & Monthly Spend

UltaHost Dedicated EPYC VDS 142,100 IOPS ($37.50/mo) Hostinger KVM NVMe 133,400 IOPS ($10.49/mo) InterServer Price-Lock KVM & ZFS 124,700 IOPS ($6.00/mo) ERPNextCalc I/O comparison (2026-11-12) | sites/common_site_config.json

Packet-to-Disk Path for frappe-bench gunicorn + python-rq + MariaDB on ERPNextCalc

1. EDGE ERPNextCalc 8000 daily ERP vouc 2. ENGINE frappe-bench gunicor 8/16/32GB 3. LIMIT gunicorn_workers=5 sites/common_site_con 4. DISK 116,000 IOPS 105 ms ledger post
9.6 / 10 INFRA AUDIT

[+] Key Infrastructure Pros

  • Stabilizes tabGL Entry & tabStock Ledger Entry InnoDB pages cache at 8000 daily ERP vouchers within 16GB.
  • Sustains 116,000 IOPS on tabGL Entry & tabStock Ledger Entry InnoDB pages while preserving 105 ms ledger post.
  • Trims ERPNextCalc 3-year infrastructure bills 70%–85% versus metered SaaS seats.

[-] Trade-Offs & Watchouts

  • Deepest UltaHost Dedicated EPYC VDS rate ($37.50/mo) requires selecting a 12m or 24m term.
  • Base OS templates need sites/common_site_config.json tuning ( gunicorn_workers=5 & background_workers=3) before peak load.

Deploy This ERPNextCalc Stack If

  • Lean teams managing 8000 daily ERP vouchers via declarative sites/common_site_config.json files.
  • Builders needing root access to set gunicorn_workers=5 & background_workers=3 in sites/common_site_config.json.

Skip This Setup If

  • Weekend throwaway demos under 72 hours (use hourly Hostinger KVM NVMe billing instead).
  • Teams unwilling to edit sites/common_site_config.json or run basic Ubuntu maintenance.
UltaHost Dedicated EPYC VDS
$37.50/mo
Claim Deal →
ERPNextCalc FAQ: How many long workers should a 16 GB ERPNext server run?

We recommend 1 to 2 long workers maximum on 16 GB nodes so concurrent Data Import jobs never exceed 2,048 MB combined RSS.