ERPNext MariaDB performance tuning
Making ERPNext's database fast: buffer pool sizing from the working set, hit ratio and utilization monitoring, swap settings and other MariaDB settings that matter for Frappe.
ERPNext operations and performance
Day-two work on a running ERPNext: database tuning, background jobs and scheduler, slow pages and reports, error tracking, email delivery, rate limits, storage growth and logs.
Scaling ERPNext reads with a MariaDB replica
Offloading heavy reports to a database replica: site_config keys, replica credentials, what gets routed to the replica and when vertical scaling is still the better step.
Troubleshooting ERPNext background jobs and workers
Diagnosing stuck or slow background work: short, default and long queues, worker counts, timeouts, failed jobs and long-running imports or reposts.
Fixing ERPNext scheduled jobs that do not run
When auto repeat, emails or backups stop: bench doctor, pending jobs, scheduler status per site, purging jobs and the Scheduled Job Log.
Fixing slow ERPNext reports and request time-outs
Handling General Ledger and stock reports that time out: prepared reports, report permissions, stock closing entries and database indexes.
Profiling slow ERPNext pages with Frappe Recorder
Finding the queries behind a slow save or page: starting Recorder, capturing requests and jobs, reading SQL and stack traces and turning findings into fixes.
ERPNext error tracking with Sentry
Sending ERPNext server and desk JavaScript errors to Sentry or self-hosted Sentry: the DSN per bench, site opt-in, tracing and profiling options and privacy settings.
ERPNext email setup and delivery troubleshooting
Getting ERPNext email to send and receive reliably: email accounts and domains, default incoming and outgoing accounts, SMTP providers, retries and emails not reaching recipients.
Rate limiting the ERPNext API
Protecting ERPNext from runaway integrations: Frappe's time-based fixed-window rate limit, choosing limit and window values, HTTP 429 handling and response headers.
Cleaning up an ERPNext database: trim tables, logs and old data
Reducing database and backup size: trimming removed columns and orphan tables, log retention, and safe dry runs and backups before cleanup.
Managing ERPNext attachment storage growth
What to do when attachments fill the disk: local file storage by design, no native S3 upload setting, private versus public files, disk planning and backup impact.
ERPNext logs and monitoring for operations teams
Knowing what a production ERPNext is doing: Error Log and Scheduled Job Log in the desk, server log files and rotation, worker error logs and what to alert on.
