Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #49817 [Scheduler] Improve triggers performance when possible (fa…
…bpot) This PR was merged into the 6.3 branch. Discussion ---------- [Scheduler] Improve triggers performance when possible | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | yes-ish | New feature? | yes <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tickets | n/a | License | MIT | Doc PR | n/a Using `\DatePeriod` for the default trigger is great as it takes care of all date/time idiosyncrasies. But for high frequencies, that does not work well and performance becomes an issue. So, this PR solves this issue by always using the fast algorithm when the frequency is expressed in seconds (int) or an ISO period (like `PT2S`) or when created from a string that uses a "simple" expression (like `2 seconds`). /cc `@upyx` Commits ------- ebcced6 [Scheduler] Improve triggers performance when possible
- Loading branch information