Event Handling - Best strategies for handling multiple events

Hello David / GH Development team,

I just raised this topic on the Rhino Developer forum but am also raising it here because it's clearly a grasshopper topic too. The question is  about event handling, in particular, how to best handle multiple 'simultaneous' events when they are triggered and what strategies are recommended.

An example of an event sequence might be this:

A user performs a 'join' on a collection of selected rhino geometry, say 20 objects, which results in the event sequence of an addition of one new object and then the deletion of the 20 previous objects. 

My questions has to do with handling these (rhino) events and how they might best fit into the grasshopper solution sequence from a performance point of view. 

In the above example what I find is that code which executes perfectly with a small number of events can become quite slow when a significant number of these 'simultanious' events occur.  

What strategies are recommended for reducing the above events instead of catching each of them?

One strategy that comes to mind is caching, also found in this example [here], but I'm curious what other strategies might be recommended.