Direct answer

Despite its name, max-tick-freq is expressed as a number of ticks between AI updates. On the documented Leaf 1.21.1 branch, a value of 20 represents up to roughly one second at 20 TPS for eligible distant entities. It is not a target of 20 updates per second.

How to check it

  1. Confirm DAB is enabled and locate performance.dab.max-tick-freq in your generated config.
  2. Test an entity behavior-sensitive farm at the nearest and farthest relevant player distances.
  3. Measure tick load plus delays in mob targeting, movement and villager activity.

What to change

Only adjust the existing value by a small amount, then restart if required by that build:

performance:
  dab:
    max-tick-freq: 20  # 1.21.1 reference example

If distant mobs react too slowly or a farm breaks, decrease the interval or exclude the affected mob type instead of applying the same large limit to all entities.

Compatibility and safety

The key and layout are sourced from the historical 1.21.1 Leaf reference; exact defaults or supported options on a new branch require a fresh version check.

Software and version notes

The cited Leaf global config page explicitly describes the 1.21.1 branch; newer Leaf builds may have different keys, defaults or feature support. Verify config/leaf-global.yml generated by your actual server.

Verify the result

Verify both performance change and AI behavior at a repeatable player distance. Keep the prior value ready for immediate rollback.

References