Our pure JavaScript Scheduler component


Post by derreck »

Hi!

Noticing a costly performance cost associated to how the Scheduler is sanitizing (unsafeHtmlRender) every row in our app, particularly the non-visible rows.

Is there a way to defer the sanitization until the row is in view or somehow sanitization process know the difference between visible and not visible?

Another thing to note, is that when expanding rows it sanitizes all rows and not just the ones being expanded.

Thanks,
Derreck


Post by saki »

Would you please give us a runnable showcase or steps to reproduce? We will analyze it and improve performance where possible.


Post by derreck »

Hi Saki,

We were able to narrow down the performance issue to an implementation issue on our side.

I do however have another question, the render listener seems to re-emit elements that were previously rendered. Is there a way to minimize this or have a growing buffer to not re-render the same elements repeatedly?

You can see this when you scroll vertically and have a listener on the 'render' action.


Post by saki »

Open please another thread with this issue. Put there exact steps to reproduce (render listener code you used), method of detection that same elements were re-rendered (removed and created?) when not needed and also if you used a custom renderer possibly with custom elements. We will analyze it and suggest the performance improvements.


Post Reply