Extremely slow web UI performance

[Luke 37021]

As far as the remote access goes, i would suggest checking out our Connection Troubleshooter. Please try the steps listed there and let us know exactly what succeeds and what fails. thanks !

[nagetech 66]

@@Luke Hey Luke do you think it would be possible to implement something in the admin panel to help maintain the SQL database? Might be useful to users with long standing installs to make sure the database is as lean and mean as possible.

[bozrdnag 73]

 

I had the same problem with emby-server on linux.  Rather than wiping out the db and starting over I chose a different approach:

systemctl stop emby-server
sqlite3 /var/lib/emby-server/data/library.db "VACUUM"
sqlite3 /var/lib/emby-server/data/library.db "ANALYZE"

sqlite3 /var/lib/emby-server/data/library.db "REINDEX"
systemctl start emby-sever

 

I am running Emby Server in a Docker container on unRAID and I would like to do this.  The problem is that when I run the first line I get an error saying:

systemctl: command not found

Can anyone tell me how to stop the emby-server process from the container console?

[Luke 37021]

@@Luke Hey Luke do you think it would be possible to implement something in the admin panel to help maintain the SQL database? Might be useful to users with long standing installs to make sure the database is as lean and mean as possible.

 

It's possible, the problem is that is you will not be able to use the server at all while this is happening. We also won't be able to show a progress bar for it either. Inevitably people are going to kill the process because they don't like how long it's taking, which then means we're going to have to troubleshoot potentially corrupted databases.

[MikePlanet 140]

It's possible, the problem is that is you will not be able to use the server at all while this is happening. We also won't be able to show a progress bar for it either. Inevitably people are going to kill the process because they don't like how long it's taking, which then means we're going to have to troubleshoot potentially corrupted databases.

Didn't you do such maintenance automatically in the past? It seems actually really useful - I did a compress/reindex of the library.db via sqlite explorer and it reduced the response time in the GUI from 10-20 seconds down to 1-5 seconds. So indeed it seems necessary at least for larger databases to keep the system "snappier"...

[Luke 37021]

They were actually db upgrades, which we will never do again, for similar reasons.

[Luke 37021]

 

I had the same problem with emby-server on linux.  Rather than wiping out the db and starting over I chose a different approach:

systemctl stop emby-server
sqlite3 /var/lib/emby-server/data/library.db "VACUUM"
sqlite3 /var/lib/emby-server/data/library.db "ANALYZE"

sqlite3 /var/lib/emby-server/data/library.db "REINDEX"
systemctl start emby-sever

 

How to vacuum your emby server database:

 

https://emby.media/community/index.php?/topic/75510-42032-vacuum-database-config-switch/

 

Thanks.

[morpheus1 1]

 

I had the same problem with emby-server on linux.  Rather than wiping out the db and starting over I chose a different approach:

systemctl stop emby-server
sqlite3 /var/lib/emby-server/data/library.db "VACUUM"
sqlite3 /var/lib/emby-server/data/library.db "ANALYZE"

sqlite3 /var/lib/emby-server/data/library.db "REINDEX"
systemctl start emby-sever

Sorry for digging this up, but is this still applicable to the current server version for linux?

Edited May 3, 2020 by morpheus1

[Luke 37021]

Sorry for digging this up, but is this still applicable to the current server version for linux?

 

This is: https://emby.media/community/index.php?/topic/75510-42032-vacuum-database-config-switch/