-
-
Notifications
You must be signed in to change notification settings - Fork 394
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
Ombi slow after mysql migration #5121
Labels
Comments
Submitted as a bug due to the significant performance hit, but could also easily be an enhancement request instead. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Since migrating from SQLite to MySql, Ombi has not been as responsive as before and the performance decrease is extremely noticeable when using the IOS clients.
As part of trying to optimize MySql, we noticed simply adding a few more "Indexed" columns might help, and afterwards performance is as good as when using Sqlite.
Newly indexed columns:
ImdbId , TvDbId , TheMovieDbId
Also, in the PlexServerContent table, these are defined as "longtext" instead of "int" as in other tables. Since we didn't want to convert the data type in this table, we created indexes using a fixed numbers of characters. Example:
CREATE INDEX idx_TvDbId ON PlexServerContent(TvDbId(10));
CREATE INDEX idx_TheMovieDbId ON PlexServerContent(TheMovieDbId(10));
CREATE INDEX idx_ImdbId ON PlexServerContent(ImdbId(12));
Ombi Version
4.43.5
What platform(s) does this occur on?
Docker
What database are you using?
MySQL
Relevant log output
The text was updated successfully, but these errors were encountered: