Performance And Large Projects

RevoGrid virtualizes the task table and timeline projection. Preserve that advantage by updating project data through public collections rather than rendering parallel task DOM or reading state back from cells.

Recommendations

• Use stable task and linked-entity IDs.
• Replace only collections that changed and keep wrapper inputs memoized or reactive at the correct boundary.
• Batch related task, dependency, calendar, resource, and assignment changes before triggering a new schedule pass.
• Keep custom cell and task-bar renderers pure and inexpensive.
• Limit visible marker and time-range overlays to information users need in the active view.
• Prefer column presets over rendering every analytical field at once.
• Measure scheduling separately from browser rendering with the Enterprise scheduler benchmark.
• Test representative hierarchy depth, dependency density, resource assignments, and timeline span—not only row count.

Current Boundary

Virtual rendering is implemented. A server-side, date-windowed Gantt project model is not currently part of the public contract, so the complete linked project graph must be available to the client scheduler. See Limitations before designing very large remote projects.

Run the local scheduler benchmark with:

pnpm --filter @revolist/revogrid-enterprise bench:gantt