Consider disabling triggers on large processes

[chrispenny]

EG: Performing a duplicate on a Page that has many Elements could cause issues if there are a large number of touches/cares.

Can we identify such actions, and find a way to not trigger our actions during those actions?

[chrispenny]

I've had a bit of a play around with "large" processes such as duplicate().

I really didn't notice any slow down of the actions when I ran them on pages that had (roughly):

• 10 Blocks each
• 3 of the Blocks each contained between 5 and 10 Items (EG: Carousel Blocks)
• Each Item had 1 Image
• Half of the Items also had a Link

I think we could potentially create some sort of State and allow devs to enable/disable cache key generation during processes that they nominate, but I'd be keen to hear that it's a problem before we do that.

[chrispenny]

Closing this, as we haven't had any complaints about bulk actions.

Anyone can please feel free to comment on here if they are having performance issues, and we'll have another look into it.