I would like to start a conversation about optimizing the performance of Acumatica ERP. This is a pretty general statement, as some processes or screens may require more heavy lifting than others, so there is of course no one-size-fits-all for performance tuning. With that said, let’s define performance as “the 80/20 rule for most users most of the time”. This means that most screens will load within 1 second, and most users will not be waiting more than a couple seconds for most processes to finish.
With that rather general benchmark as our guide, what has everyone found as being important to the performance of various aspects of Acumatica ERP? I have thrown some pretty serious firepower at this system (think $6,000/month bill on AWS for virtual Windows Server + high performance RDS instance). I have noticed with this particular setup, things are pretty fast most of the time. However, I still see lag, especially if the system has not been touched in a while (right now there are only 1-2 simultaneous users at a given time). So the question of course becomes, if we can throw $6k/month at the problem, and still see lag with 1-2 users, what happens when you add 100+ simultaneous users?
So I would like this to be a freeform discussion about which aspects of server performance impact which aspects of the system the most. For example, I have noticed that using NVMe drives has a pretty significant impact on performance. This suggests that fast disk is pretty important to the operation of Acumatica. Per Acumatica’s recommendations, I spun up my server with RDS on Amazon, and per our bill I think it’s probably pretty performance. However, putting the SQL Server on a dedicated server with NVMe disks may move the needle even more? Hard to say.
With that….I’ll let anyone else comment who might have some thoughts or suggestions. Keep in mind, I am not asking for performance tuning relative to hosted Acumatica. You are free to throw whatever server, Redis cache, whatever at the system to make it go. Assume you have total control over the stack. The exercise here is not performance tuning assuming an instance hosted by Acumatica itself. Also, assume the latest version of Acumatica.