How much workload can ERPNext/Frappe handle in production?

ERPNext
1

I’m trying to understand the practical scalability of ERPNext/Frappe for a production deployment.

One of our use cases is expected to generate approximately:

  • ~5,000 Projects per year

  • 10–20 Tasks per Project

  • Around 50,000–100,000 Tasks per year

Would this volume be considered small, medium, or large for ERPNext?

I’m interested in hearing from people running ERPNext in production:

  • How many Projects/Tasks (or similar records) does your instance handle?

  • At what scale do you start noticing performance issues?

  • Are there any known limits or best practices for handling this volume?

  • Does ERPNext/Frappe comfortably support datasets of this size with proper server resources and database tuning?

I’d love to hear about real-world experiences and any recommendations for planning ahead.

2

@spathakvincular.in Frappe/ERPNext can handle your use-case if it’s only related to your projects database, but if you want other modules too, you need to do some tweaks in your servers or you can directly connect with frappe team for hosting services.

3

For this workload, I would consider it a medium-sized deployment rather than a large one.

5,000 projects/year with 50k–100k tasks annually is not an extreme volume for ERPNext/Frappe. The bigger factor is usually not the number of records alone, but how the system is being used:

  • Number of concurrent users

  • Background jobs and scheduled tasks

  • Custom scripts/hooks

  • Report complexity

  • Database queries

  • File attachments and integrations

A properly configured Frappe setup with good server resources, database optimization, and proper indexing should be able to handle this scale comfortably.

I would suggest planning for scalability from the beginning:

  • Monitor MariaDB performance and slow queries

  • Keep heavy reports optimized

  • Move long-running processes to background jobs

  • Avoid unnecessary custom scripts on document events

It would also be useful to know:

  1. How many users will access the system daily?

  2. Are you planning to use only Projects, or also Accounting, HR, Stock, Manufacturing etc.?

The total workload across all modules usually matters more than the number of Project/Task records alone.