Direct answer
Fluid flow can schedule block updates, especially in newly opened areas or rapid piston/dispenser designs. A static water source is not the same load as continuously changing fluid.
How to check it
- Find whether spikes occur when fluids spread, retract or are continuously dispensed.
- Profile during active changes while checking for observer feedback and repeated block updates.
- Compare the same machine with fluid propagation stopped on a disposable copy and inspect whether another plugin is reacting to block physics.
Example: A stationary river in a loaded chunk usually differs from a clock-operated dispenser alternating water every tick. Turn off the latter temporarily when interpreting the profile.
What to change
Reduce unnecessary fluid updates and repeated dispenser cycling. For technical farms, prefer measured scheduling or build redesign instead of global block tick limits.
Software and version notes
Paper’s maximum fluid-tick safety setting prevents extreme queues; raising it indiscriminately can worsen stalls, while reducing it can delay world behavior. Never treat it as a free speed multiplier.
Verify the result
Check fluid settles, item streams and farm collection still work, and the same busy scenario causes fewer spikes.