Skip to main content

​
Diagnostic Steps

Start by checking the Gantt footer for load statistics. The footer shows key performance indicators:
Footer MetricMeaningAction if High
Gantt RowsNumber of items loadedReduce with filters or lower Max Items
SkippedItems beyond the Max Items limitIncrease limit or narrow query scope
Server load timeTime taken to prepare data on the serverCheck server resources, reduce item count
ErrorsIssues encountered during loadAddress errors to avoid retry overhead

​
Step 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
Adjust Max Items: Navigate to Widget Parameters > Max Items and set a value appropriate for your project size. The default limit prevents excessive loading, but setting it too high causes slow performance.
Projects with thousands of work items can cause the Gantt to load slowly or appear blank. Use dataset filters to reduce the scope before increasing Max Items. If you must display large datasets, consider splitting the view into multiple Gantt widgets, each focused on a subset.

​
Step 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
A triangle icon with an error count badge in the Gantt footer indicates script errors. Fixing these errors can improve performance because the Gantt avoids processing broken scripts repeatedly.

​
Step 3: Verify Configuration Alignment

Performance issues are sometimes caused by configuration mismatches with Polarion administration settings:
  1. 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
  2. Check field mappings — Invalid field references (Start Field, End Field, Duration Field) cause extra error handling during load
  3. Review dependency roles — Missing or incorrect dependency roles generate errors for each affected work item

​
Step 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 clearCalendarCache endpoint

​
Step 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.

​
Performance Optimization Summary

diagram

​
Verify

After applying optimizations, reload the Gantt chart. You should now see faster loading with the footer showing a reduced item count, zero skipped items, and no error indicators. Check the server load time in debug mode to confirm improvement.

​
See also

Support TicketsSource Code
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/LoadInfo.java