[bug] Fast-HTML uses 100% of a core, reducing performance and causing issues. #843
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#843
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
OTP
Extra details
Debian Linux.
Version
3.13.2-0-g050bc74
PostgreSQL version
15
What were you trying to do?
Akkoma, at some point, ends up using 100% of a CPU core in the Fast-HTML library calls. This is an issue and causes performance problems and I don't think this is intended behaviour, since it is persistent in long-term, but disappears for some time after a restart.
What did you expect to happen?
For it to not use 1 CPU core constantly or, if it is intended, to persist after a restart.
What actually happened?
It kept using 1 CPU core, and disappeared after a restart, although, I believe this is likely to come back.
Logs
Severity
I can manage
Have you searched for this issue?
A new version of fast_html was released last month. The changelog says it updated lexbor to 2.4.0, and lexbor's changelog mentions improved performance. Perhaps worth upgrading the dependency in that case.
could be, it is still a problem, i'll wait for the next binary release and hope it'll work since we don't build it from source :)