If you expand a tree node with 1000 items in it, and that tree has an ng-template the performance is very poor. It takes 7 seconds on my machine, see here https://www.telerik.com/forums/slow-treeview-with-large-datasets Please add virtualisation to the TreeView so that not so many DOM elements (and therefore ng-templates) need to be created.
Hello Julie,
Yes, the Load more button functionality, doesn't replace the <li> elments, but just adds them to the DOM which in continuous scrolling might affect the performance. The current solution isn't a pure virtualization mechanism, rather improving the load performanec when having lots of data.
The feature is still not part of our immediate development plans.
If the feature is urgent, I can offer our Feature Acceleration program. It allows a customer to negotiate a certain component or functionality to be implemented on demand.
Please let me know if you are interested in pursuing this option at any time, and I will put you in touch with our Professional Services team to discuss your exact specifications and possible timeframes.
Regards,
Martin Bechev
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
Hi,
I just implemented the treeview with the search functionality, and had to use the "Load more" button to improve performances for treeviews with lots of data.
Unfortunately, the behavior with both those functionalities is very clunky. (eg. still shows the "Load more" button while the user didnt "load" the data, even if there is only one result after the search)
Implementing data virtualisation would fix this problem in the best way (no more need of the "Load more" button)
Aslo, kinda related, but when searching treeviews, the DOM still contains the "hidden" <li> tags, instead of just not having them, which doesnt help with performances.
As a result, the treeview is currenty not really usable with lots of data.
Hi all,
I am following you back due to the change in the status of the feature request (Completed - Unplanned), and here is why.
We previously decided to mark this feature as 'Completed,' as we considered the "Load more" to be a good substitution when it comes to improved performance. However, virtualization is different from the load more approach, and both have different usages. That is why the currently available feature is more like an alternative to virtualization.
Due to continued interest, we are reopening the feature and continuing to track the demand. Since the TreeView does not have a scrollable container by design, we are open to revisiting the design based on your feedback and engagement and support virtual scrolling.
Regards,
Martin Bechev
Progress Telerik
Enjoyed our products? Share your experience on G2 and receive a $25 Amazon gift card for a limited time!
Hi Ravi,
Currently, the Load more button is the only way ot render just a portion of data in the TreeView.
However, I noticed that the same topic was discussed in private support thread 1481730. Thus I am proceeding with closing this ticket. If any further question arises, please continue the communication there. Thank you.
Regards,
Martin
Progress Telerik
Five days of Blazor, Angular, React, and Xamarin experts live-coding on twitch.tv/CodeItLive , special prizes and more, for FREE?! Register now for DevReach 2.0(20).
Hi Team,
we are using significantly kendo components my application. I was much depress after seeing the KendoTreeView performance over the 1-lac records; even my customer's having more records then this number. Is there any way to load huge amount of data in Tree view.
Here is a quick update on this case. We have provided the "Load more button" feature of the TreeView. Please check it at the following article:
https://www.telerik.com/kendo-angular-ui/components/treeview/load-more-button/
Regards,
Svetlin
Progress Telerik
Hi Мarkosyan,
I am sorry that the Kendo Angular TreeView does not meet your project requirements. We are continuously improving the functionality of our components in order to provide a better user experience. Indeed some enhancements take more time to be considered and implemented.
We are aware of the performance issues, related to loading too many root-level items (or expanding multiple root level items which in turn contain many items), but there are system-, browser-, and Angular-specific limitations, related to rendering too many DOM elements at once.
Due to the asynchronous loading mechanism of each nested level of data and the fact that the TreeView does not have a scrollable container by design, introducing a virtual scrolling functionality is not a trivial task. That is why we are also considering to introduce a "Load more" or other similar mechanics for addressing scenarios in which the TreeView contains too many items.
However, we abstain from giving exact timelines as we would not like to make promises we might not be able to hold but our development team is aware of the need for such enhancement, and we will do our best to provide it.
Thank you for the understanding.
Regards,
Martin
Progress Telerik
+1
Have 8k records and tree doesn't works well. Very slow. So i decided to select another component for the tree
Hi Peter,
Thank you for the feature request in our feedback portal it will be considered when planning our tasks for the next queue.
Regards,
Ivan
Progress Telerik