Skip to content
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

The processing delay time is too long, resulting in inaccurate timing task time #548

Open
jinsuojinsuo opened this issue Sep 23, 2022 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@jinsuojinsuo
Copy link

1663898862219
It is recommended to make it configurable

@jinsuojinsuo jinsuojinsuo added the enhancement New feature or request label Sep 23, 2022
@linhbkhn95
Copy link
Contributor

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

@yousifh
Copy link
Contributor

yousifh commented 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.

@kamikazechaser
Copy link
Collaborator

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

@jinsuojinsuo
Copy link
Author

Why does time fluctuate

@krhubert
Copy link
Contributor

krhubert commented 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants