We have noticed a serious performance issue in the TreeList control which I have confirmed in the latest version in this Dojo: https://dojo.telerik.com/aNuKanAG.  This Dojo is a based on the TreeList in-cell editing demo from your website.

1. Open the Dojo link I provided and Run it.
2. Open your browser DevTools console so you can see console.log messages.
3. Navigate to a leaf node of the tree if it isn't already open by default; ex: Daryl -> Guy -> Buffy -> Hyacinth
4. Click in and out of an editable cell; ex: Ext
5. Observe the DevTools console where you will see that the 'rendered XXX' text has been written for EVERY CELL in the entire tree.
6. Expand/collapse the closest parent group
7. Again, observe that EVERY CELL has been re-rendered

I was trying to figure out if there was any good reason for this.  In the Dojo above all data are nested under a single parent.  So, I created another Dojo but this time there are two  separate parent groups: https://dojo.telerik.com/OcEmAgIz.  This Dojo is based on the Binding to local data demo from your website.

1. Open the Dojo link and Run it.
2. Clear the DevTools console so you can see a clean display of results for the next action.
3. Expand and collapse a child group of Daryl Sweeney.
4. Observe the console log results: you will see that Dan Sweeney was also re-rendered.

The problem here is that these re-renders are very expensive.  Imagine if the call to console.log was instead something else that might need a bit of computation time to complete.

The simple act of expanding and collapsing a group from an unrelated part of the tree, or simply opening and closing an editable cell should not result in the entire tree being re-rendered.  This is a serious performance issue, and seems completely unnecessary.

What I have demonstrated in the Dojos I created is that Kendo is re-rendering the ENTIRE structure. The goal of this feature would be to rerender only the specific cells of the treelist that have been impacted by an edit.