2025-03-20, 07:38 AM
Hi all,
Before I go putting in a feature request, I wondered if there are already any planned improvements to how searching is handled, particularly for large libraries. I understand the index is housed in an SQLite DB which is directly queried as part of a search. I wouldn't say a couple of seconds is particularly 'slow' considering the size of my library, however it would be great to see if said index could be housed in a caching layer such as Redis or something in order to return results within ms.
I know there's an external search proxy available, but I don't like the idea of bolting on third party completely separate services to my set up.
Thanks!
Before I go putting in a feature request, I wondered if there are already any planned improvements to how searching is handled, particularly for large libraries. I understand the index is housed in an SQLite DB which is directly queried as part of a search. I wouldn't say a couple of seconds is particularly 'slow' considering the size of my library, however it would be great to see if said index could be housed in a caching layer such as Redis or something in order to return results within ms.
I know there's an external search proxy available, but I don't like the idea of bolting on third party completely separate services to my set up.
Thanks!