-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
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
CPU Usage / Locked Database #246
Comments
Thanks for opening this issue! I'm not entirely sure why you're getting errors about the database being locked, I haven't seen any errors with the hishtory server like this before. What kind of database are you using with your server, postgres or sqlite? Though looking at your log did make me realize that for self-hosted instances we likely don't need to track usage stats (since those are primarily useful for me to keep track of metadata about the shared production instance that I run). #250 disables this tracking which I'm hoping might reduce load for you (though I don't expect it to completely solve your issues). |
@ddworken Cool, thanks! I'm running sqlite so perhaps that's part of the issue. I am also using the Linuxserver.io image. Is it possible to import the existing history into Postgres if I go that direction? Thanks. |
Hey, I realized my sqlite database is over 4 gigs. Just wondering if it's possible to decrypt/convert/migrate somehow to Postgres to possibly help with the concurrency lock I may be seeing. Thank you again. |
Hello,
I saw a few prior threads about both CPU usage and a locked DB but wasn't sure if it was a similar situation. My CPU load for the container pegs at aronund 100% and I'm not sure why. I'm using this on 3 or so hosts and hosting the server within a docker container on the primary host. Here are some logs.
Thanks!
The text was updated successfully, but these errors were encountered: