On Thu, 25 Jul 2002, Andrew Sullivan wrote:
> One thing we did discover with 7.1.3 is that RI triggers on the slave
> can _really_ slow things down. It appears that triggers get slower
> and slower as a transaction rolls on, and therefore make everything
> crawl if you have a lot of rows to update (if, for instance, you stop
> replication for a while for some reason). The easy answer is to drop
> all the RI triggers, although that means you have to add another step
> in the event you have to flip over to the slave server. I haven't
> yet discovered whether the same problem persists in 7.2.
As a note, very possibly not, since IIRC Tom made some changes to
speed up the adding of the deferred triggers between 7.1 and 7.2.
However, it's probably not a bad idea to drop the triggers anyway. :)