Potential performance issues with large scale deactivcation? So we have potentially ~300,000 nodes that we would need to remove from the publishers, this is likely to occur no more than once a quarter although potential for the frequency to increase but we are not talking about multiple times a day. The delete command is called from the author to all 4 publishers like so:replicator.replicate(session, ReplicationActionType.DELETE, path, replicationOptions); although I understand I could use:replicator.replicate(session, ReplicationActionType.DEACTIVATE, path, replicationOptions); I'm thinking the second might be better as would delete leave orphaned nodes below the node supplied in the "path" variable, no?Would the removal/deactivation of these nodes cause sufficient load on the publishers to take them offline or is the deactivation handled on a separate thread to the rendering of pages? If there is a risk to the site do you have any suggestions to reduce the risk? Considering moving the nodes that we need to delete on each publisher and then del
