We currently have dynamic datasource (clients can wire it up to datasets they define) and we've seen a problem where some of these datasets have 200+ columns. (whether or not that should be allowed is debatable).
Enabling virtual scrolling made a huge difference in load and scrolling performance, but wondered if kendo already virtualized dom elements for columns. (if we have 200 columns, but only 20 of those are on screen, not drawing the rest may be hugely beneficial).
If not, any recommendations other than just rendering fewer columns to improve performance? Our page size is set to ~20 records, and we can see that reflected in actual dom elements in the browser.
Thanks!
Enabling virtual scrolling made a huge difference in load and scrolling performance, but wondered if kendo already virtualized dom elements for columns. (if we have 200 columns, but only 20 of those are on screen, not drawing the rest may be hugely beneficial).
If not, any recommendations other than just rendering fewer columns to improve performance? Our page size is set to ~20 records, and we can see that reflected in actual dom elements in the browser.
Thanks!
