Thank you.
And, as some general feeback to the thread, I do have to say Plex is feeling noticeably more responsive, but I wouldn’t say it is popping up search results as fast as I type as others have mentioned. However, the results are displayed only a split second after I finish typing. Maybe I’m just a fast typist.
Overall, quite happy with the results of the tool.
This depends on:
DBRepair.ah for v1.0.10 - Prevent negative watch counts :
File header says “ Version=“v1.0.9””
v1.0.10 - Prevent negative watch counts
Header and strings updated – (oops)
Hello!
I was on reddit reading how to optimize Plex database and came across this thread.
Unfortunately, I’m using Plex on Truenas Scale (Truecharts version) and I can’t find a way to get your app to work.
I might be wrong, but from what I’ve seen you only need the data stored inside “Library/Application Support/Plex Media Server”
I can mount the Plex volume into a specified path thanks to heavyscript. It give me something like: /mnt/MY_POOL/mounted_pvc/plex-config/Library/Application\ Support/Plex\ Media\ Server/
With all these folders inside:
Cache Codecs ‘Crash Reports’ Diagnostics Drivers Logs Media Metadata ‘Plug-in Support’ Plug-ins Preferences.xml Scanners ‘Setup Plex.html’ Updates
I think that the missing part might be sqlite3, but it seems to be installed on Truenas:
root : sqlite3
SQLite version 3.34.1 2021-01-20 14:10:07
Enter “.help” for usage hints.
Connected to a transient in-memory database.
Use “.open FILENAME” to reopen on a persistent database.
I don’t know if it’s possible and I can’t find anyone who asked the question on this thread, that’s why I’m asking it.
Thank you anyway !
You missed a key piece of info then started down the 
hole 
sudo docker exec -it plex /bin/bash
# extract from downloaded version file name then cd into directory
tar xf PlexDBRepair-1.0.0.tar.gz
cd PlexDBRepair-1.0.0
chmod +x DBRepair.sh
./DBRepair.sh
On systems with Plex in a container:
Suggest you take a few minutes and read the entire README.md
Yeah I saw that, however the issue is that I’m not able to stop PMS with the script (Not available, stop manually) and since it’s running inside kubernetes, when I try kill -15 PMS (something like this) it restart the pod, so I can’t run the script
I must be missing something but I don’t know what.
Did you think to turn off health checking so it doesn’t poll for the PMS process???
ALL:
I am considering adding another function to DBRepair.
Specifically,
As currently written,
Given there are cases where the PhotoTranscoder directory has grown to ridiculous sizes, the most I’m willing to do is count the number of files which would be removed but even this will take time. I don’t want to waste even more time finding out how much disk space will be recovered (UNLESS that’s wanted)
Thoughts?
DBRepair-Development-1.02.99.tar (70 KB)
Great idea! 
For Windows too, please? 
Luv it, great idea. Thanks Chuck
Gets my vote. I’ve been nuking this cache weekly via a cron job for years. The cache is just bloat, or at least it is based off my users usage of plex.
FYI… feature request thread here Cache/PhotoTranscoder Folder Size Sanity Check where a bunch of us done analysis of the cache and how bad it is.
I’ve got many many duplicates of many many files in the Cache/PhotoTranscoder folder.
But I’ve never seen files older than about a month. Plex is deleting old files reliably for me.
Does anybody have older files in that folder?
This would be a great feature. Indicating the number of files which would be removed is sufficient.
Chuck, FWIW, I just checked my PT folder. It’s 20GB with about 120k files and 256 folders. Not a single file is older than 30 days. So, I guess that shows that the cache CAN be well behaved
I like the idea of your very useful tool becoming even more useful so it gets my vote. I don’t need disk space recovered info; having the count is good enough to identify if the expected cache clean-up was misbehaving.
Much appreciated!
Difficult choice time… 
“purge” - “Purge old files from PhotoTranscode cache”
“remove” - “Remove old files from PhotoTranscode cache”
My only concern is future development .
I’ve toyed with “Clear”, “Clean”, “Purge”, “Remove”, and “Delete”.
Delete - Can imply way too much
Clear - Not descriptive enough (clear what? the screen? - lol)
Clean - “clean the keyboard?” – lol
Purge & Remove seem best candidates.
I will change the numbering, I’ll move this down into its own “block” of command numbers so it’s not confused with primary functionality.
Thoughts?
Input?
Purge and Remove, hopefully that will neutralize / minimize the insane cancerous growth of Photo Transcode cache.
As for Command or Ranking, (Lower) and optional would be a intuitive solution.
I vote for “Remove” as Purge seems too … dramatic?
Either is totally fine really; it’s easy to overthink these things though and it’s not like you can’t change it later.
And putting it separate from the DB cleaning options makes sense to me.
But who doesn’t like drama?
