I am noticing serious slowdowns on my DS918+, especially in varying client menus and transcoding, with remote access being unstable altogether. It appears I have quite a few slow queries to my database, so I am unsure where to start with troubleshooting.
Unfortunately, you turned off DEBUG logging thinking you’d save space.
The logs don’t work that way. The log buffer size is fixed.
We have DEBUG logging ON by default with VERBOSE logging turned OFF.
This way, we get the information we need, at the correct detail we need, by default.
Would you please reset to defaults, restart PMS, and then regenerate the conditions.
After doing so, please gather a fresh set of logs.
I would GREATLY appreciate you removing your media from the Plex metadata directory.
I hid that share deliberately and lock it down every update to keep folks from putting media there. Plex gets confused if media is placed in the Plex metadata share. It ends up monitoring itself (bad scene there).
Mar 25, 2020 06:10:11.334 [0x7f084d4e8700] DEBUG - [Notify] Now watching "/volume1/Plex/Library/4K Movies/The Hobbit The Desolation of Smaug (2013)"
Mar 25, 2020 06:10:11.335 [0x7f084d4e8700] DEBUG - [Notify] Now watching "/volume1/Plex/Library/4K Movies/The Hobbit The Desolation of Smaug (2013)/Plex Versions"
Mar 25, 2020 06:10:11.351 [0x7f084d4e8700] DEBUG - [Notify] Now watching "/volume1/Plex/Library/4K Movies/The Hobbit The Desolation of Smaug (2013)/Plex Versions/Optimized for TV"
Mar 25, 2020 06:10:11.351 [0x7f084d4e8700] DEBUG - [Notify] Now watching "/volume1/Plex/Library/4K Movies/The Hunt (2012)"
I have a number of tools updating my media folders. Is it possible to create a new “PlexData” drive so I dont have to update paths across my services (and keep my media structure in tact)?
It’s not possible to customize your installation without conflicting with the next update issued.
This is a transition you’ll need to perform over time yourself.
I say this because, when I do make the change, my intent is to rename the share. I don’t plan on surrendering the share to other uses at this time.
If there’s a good reason to have “PlexData” (for the server) and “Plex” for user data, I am always open to it but would want input from the community before doing so because that alone could be confusing
Understood. It may be easier to create a media folder and just handle the migration of existing media folders. I am not sure how long that would take seeing as it’s all on one volume, but likely worth the effort to prevent any trouble down the road with my serve.
Do you think this could be the cause of the slowdowns? It seems to have intensified as my library has grown in recent months.
I don’t know what other tasking is active on your system when these slow queries occur.
If you have other media processing RAR files (or similar), those actions alone will consume the CPU. Please do remember, Synology CPUs only have about 2700 Passmarks in a quad core configuration. The typical i7-7xxx processor has 10,000 passmarks.
If those other processes are competing, Plex’s timer will fire & flag the SLOW QUERY warning. A few here and there are of no concern. When they become frequent, that’s a problem.
It’s also a sign the database is in need of optimization (done during maintenance - scheduled tasks)
