Send AXFR instead of requested IXFR if the size of the incremental transfer is too large to sensibly IXFR
This perhaps needs to be an option that can be set globally, per view, per zone, and perhaps by allow-transfer ACLs?
Large inbound IXFRs can seriously degrade a BIND slave nameserver's performance when serving clients (not necessarily from the same zones being transferred) at the same time. The slave can't control the size of the IXFR when requesting it - it doesn't know what it is going to be sent. This is therefore something that has to be set on the authoritative server that is sending the zone update.