Community
Participate
Working Groups
An example has been brought to my attention that performs very poorly, due to the fact that there is a very long list of peer children (e.g. 2000). They are each reparented (several times) when pasting in some new element(s). [Even for one element, they are reparented once for start tag, then again when end tag is inserted.] We should add some optimization for this case (e.g. re-partent all peer children as one operation), or, if that's not possible, add a new notification type of "HUGE_CHANGE" which would be detected automatically when notification grew to, say, over 10,000. In this case, individual notifcations would be abandoned, and a "HUGE_CHANGE" be sent common parent node (as STRUCTURE_CHANGED already is). We should use the "HUGE_CHANGE" event as a fall back, even if optimatations are found.
Created attachment 16922 [details] sample file that has large number of peer nodes To demonstrate the problem, paste a tag such as one below early in the list, or late in the list, and see the (huge) difference in performance. <security-role> <description>description 1</description> <role-name>role1</role-name> </security-role>
Adding my name to the cc list as we are now tracking performance issues more closely. Please remove the performance keyword if this is not a performance bug.
