mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[GH-ISSUE #889] [FEATURE REQUEST] Custom ticker value for heartbeater duration #2464
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#2464
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RiskyFeryansyahP on GitHub (Jun 2, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/889
Originally assigned to: @hibiken on GitHub.
Is your feature request related to a problem? Please describe.
Currently, in our production environment, I have 9,000 scheduled entries that run once every week and once every month. However, I've noticed that the CPU utilization on my Redis spikes continuously. You can see this in the image below.
When I investigated the reason for these CPU spikes, I disabled the scheduler in
asynq, and the CPU usage returned to normal. While examining the code for the scheduler inasynq, I found that the heartbeater insideasynqruns every 5 seconds (hardcoded) using a ticker. This process involves scanning through cron entries and performing WriteSchedulerEntries.Describe the solution you'd like
I have an idea to configure the ticker duration based on
SchedulerOpts. This way, the ticker duration is not hardcoded and can be defined through configuration when initializingNewPeriodicTaskManager.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
@RiskyFeryansyahP commented on GitHub (Jun 2, 2024):
Hi @hibiken, if you agree with my proposal, I would be happy to implement it 😄
@RiskyFeryansyahP commented on GitHub (Jun 3, 2024):
Hi @kamikazechaser, if you have time, please check my proposal request 🙏
@RiskyFeryansyahP commented on GitHub (Jun 29, 2024):
Any update guys?
@Aldiwildan77 commented on GitHub (Jul 14, 2024):
Is there any update for this @hibiken?
Your issue seems fit to me, I also had this when I had a thousand jobs