IMHO, instead of completely disabling flow control, I’d first try tuning it (flowControlTargetLagSeconds or flowControlThresholdLagPercentage) and see if that balances things out. Completely turning it off is a bit of a risky approach, but might work for your use case if you can tolerate the risks… i.e. If your secondary does fall behind significantly for unexpected reasons (e.g., network issues, cloud provider hiccups), writes on the primary could continue at full speed, and if the secondary can’t catch up, it could drop out of sync.