mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Motioneye using huge cpu #2382
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#2382
Loading…
Add table
Add a link
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?
Originally created by @antonical on GitHub (Apr 13, 2023).
Motioneye docker running on an EXSI host with 8 x Xeon E-2650 Cpu's all cpu's maxed at 100% all the time. Not recording. 6 cameras are connected.
Is this normal?
Cheers
Spart
@MichaIng commented on GitHub (Apr 15, 2023):
It all depends on hardware acceleration, which might be not made available for VM guests. Not sure what ESXi is capable of but check whether you find and enable GPU acceleration settings for VMs.
Also use tools like
htopto find our which exact process is causing this high load.Should be the case, but might be worth to test whether the bare metal install (instead of Docker) works better. A Python module should be trivial enough to install so that Docker IMO has not really any benefit, as long as you do not have a specific reason to require the additional sandboxing.