In order to reproduce your case, I used the Loading Nodes example
where the tree loads 50 000 nodes.
It took just under a second to add new node to the tree after loading the 50 000 nodes.
At the moment the more nodes you load in a RadTreeView the slower adding/removing nodes is.
That is because the layout algorithm iterates over all the nodes in order for the new node to be displayed correctly.
In a batch update operation the layout algorithm updates the layout of nodes only once at the end of the operation.
That is why if you want to be able to add/remove many nodes and not sacrifice performance you have to use BeginUpdate
methods of RadTreeView
as in the Loading Nodes example
. Otherwise, as I see your case, you will most probably have performance issues if there are lots of nodes in your RadTreeView
the Telerik team