Performance impact of multiple validateTrigger events in Ant Design Form

Determine how many validation trigger events can be added to Ant Design Form's validateTrigger prop before validation frequency causes noticeable UI lag, especially when validation logic is expensive.

The official docs list supported events but do not specify a safe upper bound; performance depends on validation complexity, component count, and device capability. Without explicit guidance, developers must empirically test or rely on debouncing strategies.

What is the practical limit on the number of events in validateTrigger that maintains acceptable responsiveness? Does including both 'change' and 'focus' increase validation calls beyond the sum of individual events? Are there documented recommendations or thresholds for limiting validateTrigger array length to avoid performance degradation?