-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request]support parameter “H” like which in Jenkins #6
Comments
Holy crap, this is a WONDERFUL idea. I absolutely love it. I will implement this in the next version without fail. Thank you!!! |
Implemented in v0.6.4. Thanks again! https://github.com/jhuckaby/Cronicle/releases/tag/v0.6.4 |
It acts just like step after *, but will add a specific step size, this helps to avoid the server in the first few seconds of every minute very busy, for example: |
For example, using 0 0 * * * for a dozen daily jobs will cause a large spike at midnight. In contrast, using H H * * * would still execute each job once a day, but not all at the same time, better using limited resources.
The H symbol can be thought of as a random value over a range, but it actually is a hash of the job name, not a random function, so that the value remains stable for any given project.
To allow periodically scheduled tasks to produce even load on the system, the symbol H (for “hash”) should be used wherever possible.
The text was updated successfully, but these errors were encountered: