vmtouch VS autoscan

VMTouch may be helpful. https://hoytech.com/vmtouch/

Just lock the file into memory using:

```vmtouch -l /path/to/binary```

You're claiming that gnome loads all of itself into memory so that it can be faster. Now there are a few reasons why I don't think that's a reasonable idea, but assuming that you wanted that... using techniques like vmtouch to keep the files in the disk cache would make it so that gnome wasn't actually using the full 1GB. The "cached" files could be evicted from the cache if some other program needed that memory. Where as loading all of gnome in at startup regardless of whether it's actually used is probably not a good idea.

It is a mainstream thing. It's enabled by default on every Windows install, as far as I know, although you may not be impressed by its understanding of what your frequently opened programs are. It's been about ten years since I ran Windows, but I used to have a batch script to read everything in a directory so that it would be in the disk cache and subsequent accesses would come from RAM. The Linux equivalent of my script is vmtouch, although that's a lot more full-featured.

vmtouch: https://hoytech.com/vmtouch/

vmtouch.

Use Cloudbox/autoscan instead. Plex Autoscan is not maintained anymore, you can see the repository is archived.

If you use *arr to manage your downloads try setting up the "Connect" section of it with Plex and only scanning when you import/add new media to save on the periodic scans for no reason, or perhaps check out https://github.com/cloudbox/autoscan as I've heard good things about this as well.

You should now use this instead: https://github.com/Cloudbox/autoscan

This tool is designed to let sonarr/radarr directly communicate with tdarr, much like autoscan is able to communicate between sonarr/radarr and plex/emby/jellyfin.

The solution to have plex refresh the metadata after a bazarr subtitle add is to use autoscan. NOT plex_autoscan, but autoscan. This is the newer version. You also need autoscan-adapter, the critical piece of the puzzle. Autoscan by itself lets bazarr/sonarr/etc notify plex to update libraries. The autoscan-adapter helps autoscan be able to actually refresh plex metadata so the new subtitles from bazarr can be found. This is all actually very easy to implement using docker-compose. Refer to the docker-compose setup in the autoscan-adapter github.

I recommand using Autoscan. If you're using the *arr stack to download your medias, it can then automatically trigger a scan. The *arr stack can do this without autoscan for jellyfin, but the advantage of autoscan is that you can plug it to any of your other means of downloading medias by just calling its webhook