Open-source developer platform to power your entire infra and turn scripts into webhooks, workflows and UIs. Fastest workflow engine (13x vs Airflow). Open-source alternative to Retool and Temporal.
I'm using Windmill on my Raspberry Pi. The first time I installed it, what annoyed me was the constant high CPU usage (>20%), so I decided to uninstall it.
Now I reinstalled it because it is a really nice tool and the only problem for me was this CPU usage problem. So I looked into the code and found the SLEEP_QUEUE env variable which sets the polling interval of the worker. I set it to 1000ms, which is far enough for my use case.
I honestly think most use cases would be fine with a higher poll interval than the default, which is 25ms.
My suggestion would be to make it more obvious that this is an important setting to reduce server load, which might be important for some people. In my case it reduces the constant load of 20% CPU to unnoticeable when idle.
Hello there,
I'm using Windmill on my Raspberry Pi. The first time I installed it, what annoyed me was the constant high CPU usage (>20%), so I decided to uninstall it. Now I reinstalled it because it is a really nice tool and the only problem for me was this CPU usage problem. So I looked into the code and found the SLEEP_QUEUE env variable which sets the polling interval of the worker. I set it to 1000ms, which is far enough for my use case.
I honestly think most use cases would be fine with a higher poll interval than the default, which is 25ms. My suggestion would be to make it more obvious that this is an important setting to reduce server load, which might be important for some people. In my case it reduces the constant load of 20% CPU to unnoticeable when idle.