Table of Contents style circle
...
Identify Performance Bottlenecks
The saying from renowned computer scientist Donald Knuth goes:
...
Ensure Sufficient Java VM Memory Allocation
The platform runs on the Java VM (JVM), and depending on the size and complexity of your apps and usage, you might need to tune the JVM heap memory size to suit your environment. If the setting is too low, the system will run out of memory resulting in OutOfMemory errors. However if the setting is too high compared the amount of physical RAM available, there might be quite a lot of swapping, in addition to overheads in garbage collection.
...
Some additional details are available at Deployment Best Practices#JavaVMConfiguration.
...
Eliminate Resource Leakage (Memory, Database Connections, Files, Network, etc)
At the platform level, Joget Workflow has been optimized and tested to ensure that there are no resource leakages.
...
The database connection usage can be monitored in your database server, or using use the upcoming v6 Database Connection Monitoring and Leak Detection feature.
...
Optimize your App and Database Queries
Joget Workflow has been thoroughly profiled and optimized to ensure that there is minimal overhead at the platform level. However, in enterprise apps that rely on dynamic data, each page request would require many database queries. Database calls are slow not just in query execution, but especially in network I/O. In most cases, database calls are the main performance bottlenecks that cause lengthy page response times and limit scalability.
...
In the upcoming v6, there will be a new Userview Caching feature to optionally cache userview pages and menus for a significant performance boost.
...
Tune the Database and Application Server
...
If there are a lot of concurrent requests to your app, it might also be prudent to tune your application server as per Deployment Best Practices#WebApplicationServerConfiguration.
Do update your database server to the latest MySQL releases. New stable database engine releases usually have performance improvments.
If you use a lot of form grids with parent and child database tables, do add indexes to your foreign key child table. This will speed up retrieval of the child form records.
...
Load Test your App and Server Sizing
There are many factors involved in determining the server specifications needed to run Joget Workflow effectively. These are some of the non-conclusive factors:
...
To determine the actual requirement for your app and usage, it is best to perform load testing in your environment. There are many free and commercial load testing available, there is an article using the open source Apache JMeter tool at Joget Workflow Clustering and Performance Testing on Amazon Web Services (AWS)
...
Introduce Clustering and Load Balancing
When you have optimized your apps, you can increase your server capacity as appropriate to handle increasing load (vertical scaling). You can also start to consider performing horizontal scaling i.e. to cluster or load balance your installation. This can not only handle increased load, but also offer high availability. Read more on this at Deployment Best Practices#ClusteringandLoadBalancing.
...