Our pure JavaScript Scheduler component


Post by richard.schoeffauer »

Dear Bryntum Team,

We currently have an application featuring 7 Bryntum Schedulers that are partnered and active simultaneously on a single browser page. As we’ve scaled up from 2 schedulers, we’ve noticed a steady deterioration in performance, particularly during scrolling.

Here is a quick breakdown of our current architecture:

  • 5 Active Schedulers: Used to visualize distinct types of events. Each has custom rendering logic, drag-and-drop logic, and right-click context menus.

  • 2 Fixed Timeline Axes: Instantiated only to serve as fixed timelines (one at the top, one at the bottom).

  • Splitter Layout: The 5 active schedulers are positioned between the fixed timeline axes and can be resized vertically via custom splitters.

Our Questions & Considerations:

  1. General Optimization: Do you have any tips or recommendations for keeping this specific setup as performant as possible?

  2. Single Scheduler Approach: Would it be significantly better for performance to consolidate everything into a single Scheduler, leveraging resource customization and custom event rendering logic instead?

Any insights or recommended best practices for managing this volume of partnered components would be greatly appreciated. Thank you!


Post by alex.l »

Hi,

  1. For performance configs please review https://bryntum.com/products/scheduler/examples/bigdataset/ configs, it uses available options.
  2. For sure 1 instance would be significantly better than 7 on 1 page. You will need to review if all you need has properties on instance (managable at runtime) and if so, that's easy to change it without need in a new instance. Otherwise you might be needed to re-create Scheduler in some scenarios. Question is too abstract to give you specific recommendations what to do.

All the best,
Alex Lazarev

How to ask for help? Please read our Support Policy


Post Reply