[GH-ISSUE #548] The processing delay time is too long, resulting in inaccurate timing task time #259

Open
opened 2026-03-02 05:20:00 +03:00 by kerem · 5 comments
Owner

Originally created by @jinsuojinsuo on GitHub (Sep 23, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/548

Originally assigned to: @hibiken on GitHub.

1663898862219
It is recommended to make it configurable

Originally created by @jinsuojinsuo on GitHub (Sep 23, 2022). Original GitHub issue: https://github.com/hibiken/asynq/issues/548 Originally assigned to: @hibiken on GitHub. ![1663898862219](https://user-images.githubusercontent.com/7435297/191880271-c4e7d460-d144-46d0-bca3-b0e68ce1b32a.jpg) It is recommended to make it configurable
Author
Owner

@linhbkhn95 commented on GitHub (Sep 23, 2022):

@jinsuojinsuo It is delayed when all queues are empty. I think it makes sense

<!-- gh-comment-id:1255951625 --> @linhbkhn95 commented on GitHub (Sep 23, 2022): @jinsuojinsuo It is delayed when all queues are empty. I think it makes sense
Author
Owner

@yousifh commented on GitHub (Sep 23, 2022):

I did some benchmarking around this issue here #506

It impacts the average time to execution for tasks. However lowering the sleep will increase the idle CPU usage of Redis. I also tested an alternative approach that can change the sleep period depending on how busy the queue is here. It will lower the latency of time to execution at the cost of more complicated code.

<!-- gh-comment-id:1256804429 --> @yousifh commented on GitHub (Sep 23, 2022): I did some benchmarking around this issue here #506 It impacts the average time to execution for tasks. However lowering the sleep will increase the idle CPU usage of Redis. I also tested an alternative approach that can change the sleep period depending on how busy the queue is [here](https://github.com/hibiken/asynq/compare/master...yousifh:asynq:faster-sleep). It will lower the latency of time to execution at the cost of more complicated code.
Author
Owner

@kamikazechaser commented on GitHub (Oct 6, 2022):

It could be added as an optional param that defaults to 1 second.

<!-- gh-comment-id:1269566822 --> @kamikazechaser commented on GitHub (Oct 6, 2022): It could be added as an optional param that defaults to 1 second.
Author
Owner

@jinsuojinsuo commented on GitHub (Oct 10, 2022):

Why does time fluctuate

<!-- gh-comment-id:1273515819 --> @jinsuojinsuo commented on GitHub (Oct 10, 2022): Why does time fluctuate
Author
Owner

@krhubert commented on GitHub (Jun 2, 2023):

Hey @hibiken, any chance to address this issue? It would be especially useful for speeding-up e2e tests.

I've made a PR

<!-- gh-comment-id:1572937585 --> @krhubert commented on GitHub (Jun 2, 2023): Hey @hibiken, any chance to address this issue? It would be especially useful for speeding-up e2e tests. I've made a [PR](https://github.com/hibiken/asynq/pull/665)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#259
No description provided.