To get the best performance from GanttPRO, it is important to consider several factors that may affect speed, especially when handling large amounts of data and complex projects.
We have gathered recommendations to help you optimize GanttPRO’s performance and avoid potential slowdowns. Follow these tips to make the most of GanttPRO’s features and ensure a smooth experience.
Projects and project portfolios
1. Control the number of tasks in a project or portfolio
GanttPRO supports up to 10,000 tasks within a single project or portfolio while maintaining stable performance on mid-range systems (Intel i5, 8GB RAM, 8th gen and beyond). Exceeding this limit may lead to slowdowns, which are usually caused by data volume rather than platform restrictions.
We’re continuously improving performance and have already outpaced competitors, whose solutions typically handle only 300–600 tasks. Especially, when it comes to automatic calculations in the auto-scheduling feature.
2. Archive inactive projects
Keeping a large number of inactive projects can slow down the system. Archiving these projects helps improve performance significantly while still allowing access. You can restore them anytime if needed.
💡 Check here how to archive projects.
3. Avoid adding all account projects to a single portfolio
During user interviews, we’ve noticed that some users add all their account projects into one portfolio to avoid switching between individual projects.
However, you have to consider that as the portfolio grows, its performance may slow down. To prevent potential performance issues, we recommend organizing projects into multiple portfolios instead.
Gantt chart
1. Avoid adding dependencies with parent tasks
Having a large number of dependencies between tasks, especially when using the auto-scheduling feature, can slow down performance. During user interviews, we've sometimes observed excessive use of dependencies, such as 400 dependencies for just 100 tasks.
It's better to avoid setting dependencies with parent tasks, as this goes against recommended planning practices. The screenshot below shows the correct way to set dependencies between tasks from different groups:
2. Avoid viewing large projects in hours
The hourly Zoom scale is ideal for short projects with a small number of tasks, such as event planning, for example.
For larger projects, we recommend avoiding this zoom level, as it can make it harder to visualize and manage the project properly.
💡 Read more about Zoom here.
3. Disable critical path display when not in use
Keeping the critical path always enabled in projects with many tasks can slow down performance. We recommend disabling it when not needed to prevent overloading the system with unnecessary calculations.
4. Disable baseline display when not in use
Keeping the baseline always enabled in projects with a large number of tasks and data can slow down performance. We recommend disabling it when not needed to avoid long data load times and improve overall performance.
Workload
1. Reduce date ranges in the Workload view
Using an extensive date range can negatively impact performance. If you don’t need to edit or view the workload over an extended period, we recommend shortening the range to a few months to improve performance.
2. Collapse the Workload tab when not in use
We recommend collapsing the Workload tab whenever you’re not using it. This will help improve performance in projects with many tasks and resources and allow you to see more tasks on the screen.