Diagnostic Steps
Start by checking the Gantt footer for load statistics. The footer shows key performance indicators:1
Reduce the Item Count
The most impactful performance optimization is reducing the number of items the Gantt needs to load and render.Narrow the dataset query:Configure the widget’s dataset to filter for only the relevant work items. Use Polarion Lucene queries to scope the data:
- Filter by status (e.g., exclude closed items)
- Filter by date range to show only current sprints
- Filter by work item type to show only relevant types
2
Review Custom Scripts
Item scripts execute for every loaded work item, so complex scripts multiply their impact across the entire dataset.
- Simplify item scripts — Remove unnecessary API calls or complex logic
- Avoid heavy Polarion API calls in scripts — Each call adds server round-trip time
- Check for script errors — Failing scripts may cause retry loops that slow loading
3
Verify Configuration Alignment
Performance issues are sometimes caused by configuration mismatches with Polarion administration settings:
- Verify enumeration values — Ensure that work item type IDs, link role IDs, and field IDs in the widget parameters match the values defined in Polarion Administration
- Check field mappings — Invalid field references (Start Field, End Field, Duration Field) cause extra error handling during load
- Review dependency roles — Missing or incorrect dependency roles generate errors for each affected work item
4
Optimize Working Calendars
If you use working calendars, calendar resolution adds processing time per work item. Consider:
- Using a shared calendar project rather than per-user calendars for simpler configurations
- Clearing the calendar cache after making calendar changes by calling the
clearCalendarCacheendpoint
5
Check Gantt Version
Newer Gantt versions include performance improvements. Check the version displayed in the Gantt footer and update if you are running an older release.