Factory & MRP Workloads
ERPNextCalc Manufacturing, Multi-Level BOM & MRP Scaling
ERPNextCalc treats Manufacturing and MRP benches differently from plain accounting sites because recursive BOM explosion and Production Plan runs spike Python long-queue memory.
In our audit of 80-seat factory deployments, raising rq_long workers from 1 to 2 and setting worker_timeout to 300 seconds eliminates timed-out Production Plan runs.
ERPNextCalc Memory Profile for BOM & Production Plans
Exploding a 400-item multi-level BOM loads nested Item, Warehouse Bin, and Stock Ledger valuation rows into Python dictionaries, peaking near 950 MB–1,024 MB per long worker.
We recommend dedicating at least 16 GB RAM (7.2 GB InnoDB + 2 long RQ workers) for factories running continuous shop-floor Job Card updates.
ERPNextCalc Stock Ledger Reposting Discipline
Backdated Stock Entries trigger Frappe Repost Item Valuation jobs on the default queue. Keeping 3 default workers prevents backdated adjustments from delaying live Delivery Note submissions.
We advise scheduling bulk Cost Center and Stock Reconciliation imports outside active shift handovers.
ERPNextCalc Manufacturing Bench Parameter Target
# ERPNextCalc Factory Target (80 Users / 8 vCPU / 16 GB RAM)
gunicorn_workers = 17
rq_short = 2 | rq_default = 3 | rq_long = 2
mariadb_innodb_buffer_pool_size = 7372M
Factory Scale vCPU / RAM RQ Split (S/D/L) InnoDB Pool (45%)
25–45 shop-floor users 4 vCPU / 8 GB 2 / 2 / 1 3,686 MB
50–110 shop-floor users 8 vCPU / 16 GB 2 / 3 / 2 7,372 MB
120–250 shop-floor users 16 vCPU / 32 GB 4 / 4 / 3 14,745 MB
Modeling factory BOM and Stock Ledger concurrency in ERPNextCalc keeps assembly-line Work Orders moving without queue backlogs.
Test the 80-user Manufacturing preset inside the ERPNextCalc Parameter Ribbon.
ERPNextCalc Factory & MRP Workloads FAQ
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
Copy [ULTA20] & Open UltaHost
Chart 1: tabGL Entry & tabStock Ledger Entry InnoDB pages throughput (116,000 IOPS) for ERPNextCalc nodes.
ERPNextCalc FAQ: Why do backdated Stock Entries slow down ERPNext?
Each backdated stock transaction forces sequential recalculation of moving-average or FIFO valuation queues across subsequent ledger entries.
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.5
/ 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.
More frappe-bench gunicorn + python-rq + MariaDB Sizing Guides
ERPNextCalc FAQ: Should barcode Job Card tablets use Gunicorn or API tokens?
API key/secret headers hit Gunicorn statelessly without allocating browser Desk session state in Redis Cache.