We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After we tackled the OOM issues (see e.g. #107) users using HomeAssistant OS 10 also had issues with CPU usage from FR24Feed.
The root cause is the same as the OOM issue, the removal/change of ulimit.
ulimit
I did a fix in my repo by setting a ulimit also for FR24Feed- see MaxWinterstein/homeassistant-addons#151 (comment) and MaxWinterstein/homeassistant-addons#160
I am kinda confused about two things:
ULIMIT_N
thttp
My proposal on that would be to
HTTP_ULIMIT_N
FR24FEED_ULIMIT_N
run
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
After we tackled the OOM issues (see e.g. #107) users using HomeAssistant OS 10 also had issues with CPU usage from FR24Feed.
The root cause is the same as the OOM issue, the removal/change of
ulimit
.I did a fix in my repo by setting a ulimit also for FR24Feed- see MaxWinterstein/homeassistant-addons#151 (comment) and MaxWinterstein/homeassistant-addons#160
I am kinda confused about two things:
ULIMIT_N
that is a system-wide setting according to the README, but in fact, it is just used for thethttp
service.My proposal on that would be to
ULIMIT_N
to something likeHTTP_ULIMIT_N
and add a newFR24FEED_ULIMIT_N
property. Maybe make the ulimit thing generic for allrun
files.The text was updated successfully, but these errors were encountered: