Performance Tips
As your project grows to hundreds or thousands of tasks, GlidePath’s performance remains responsive with these practices.Feature Spec Reference
Module 15 — Performance & ReliabilityLarge Schedule Management (500+ Tasks)
Best Practices
-
Use Hierarchy Effectively
- Organize tasks in a logical WBS (2–4 levels deep)
- Collapse parent summary tasks to reduce visible rows
- Navigate using outline expand/collapse buttons
-
Optimize Dependencies
- Avoid excessive linking; only link truly dependent tasks
- Use summary-level dependencies instead of linking every task
- Example: Instead of linking 20 tasks from Phase 1 to 20 tasks in Phase 2, link the Phase summary tasks
-
Use Constraints Sparingly
- Constraints can slow CPM recalculation
- Prefer dependencies over constraints when possible
- Remove unnecessary constraints after schedule is finalized
-
Zoom and Filter
- Zoom out (Month view) to see high-level overview without redraw lag
- Filter task list to show subset (e.g., critical path only)
- Navigate to specific date range instead of scrolling entire project
Zoom Performance
- Day zoom: Slower, more detail; use for near-term (1–2 months)
- Week zoom: Good balance; standard view
- Month zoom: Fastest, high-level; use for overview
CPM Recalculation
When Recalculation Happens
CPM automatically recalculates when:- Task duration changes
- Task date changes
- Constraint added/removed
- Dependency added/removed
- Calendar changes
Optimizing Recalculation
- Batch Edits: Make multiple changes before clicking outside, minimizing recalculations
- Turn Off Real-Time Calc (if available): Recalculate manually after bulk changes
- Archive Completed Phases: Move completed work out of active schedule
- Split Large Projects: For 1000+ task schedules, consider splitting into sub-projects
Calendar and Working Day Performance
- Large holiday calendars: More holidays = slower recalculation
- Non-standard work weeks: Custom calendars may impact performance
- Simplify if needed: Use default Mon–Fri calendar if possible; add specific holidays only
Data Entry Best Practices
- Import over Manual Entry — Importing 100 tasks is faster than creating them one by one
- Prepare Data First — Get all task info ready before import to minimize back-and-forth edits
- Link Dependencies Last — Create all tasks first, then add dependencies in bulk
Export Performance
- Exporting large schedules (500+ tasks) may take 10–30 seconds
- Exporting to CSV is faster than PDF (PDF requires rendering)
- Use “Visible Tasks Only” export to reduce file size
Accessibility Performance
- Screen Readers: Large Gantt charts may be slower with accessibility features enabled
- Zoom to Detail Level Needed: Don’t run screen reader on entire 1000-task chart; zoom/filter first