windmill worker cpu load? #1714
-
Beta Was this translation helpful? Give feedback.
Answered by
rubenfiszel
Jun 12, 2023
Replies: 1 comment 4 replies
-
It's very likely coming from the workers + db. The way queuing work on the postgresql implementation (there is a redis one that would consume less) is that worker poll every 50ms the database for new jobs. That is a lot of polling which creates load on both the db and workers. 50ms is low but guarantees super low latency with sufficient number of free workers.
You can adjust the frequency if you'd like by setting SLEEP_QUEUE as env variable to the workers to anything higher than 50 |
Beta Was this translation helpful? Give feedback.
4 replies
Answer selected by
helmut72
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's very likely coming from the workers + db. The way queuing work on the postgresql implementation (there is a redis one that would consume less) is that worker poll every 50ms the database for new jobs. That is a lot of polling which creates load on both the db and workers. 50ms is low but guarantees super low latency with sufficient number of free workers.
In most cases, that wouldn't be an issue since:
You can adjust the frequency if you'd like…