Performance improvement suggestion for searches in Emby

[Edrock200 53]

In parsing through the debug logs for a different issue, I noticed something interesting. When someone runs a search within emby, the db queries come in one letter at a time. e.g. if I search for "avengers", the db queries come in as:

a

av

ave

etc...

As far as I can tell, the previous queries don't terminate when the next one is submitted. So for "avengers" emby kicks off 8 searches, and the first few I would imagine are very intensive as querying the db for anything with "a" in it would return a ton of results, and wouldn't be very useful in most use cases I would imagine.  If my understanding is correct, I would recommend a few possibilities:

Add a setting for minimum search characters, e.g. 3 or more

Allow a 2-3s delay between search executions of letter inputs, if the user enters another letter, reset the counter.

Alternatively, create a submit button so a search isn't executed until the user enters the entire search parameter.

Appreciate the consideration.

[Luke 42083]

Quote

Allow a 2-3s delay between search executions of letter inputs, if the user enters another letter, reset the counter.

Hi, I think generally speaking this is a long time to wait, but it has been increased slightly in the upcoming 4.8 server release. It is still under 1 second though.

[Edrock200 53]

4 hours ago, Luke said:

Hi, I think generally speaking this is a long time to wait, but it has been increased slightly in the upcoming 4.8 server release. It is still under 1 second though.

That's great! Thank you. Is this between actual letter inputs or can it sense remote activity? E.g. if using the remote to scroll from letter A to letter M, will it not search while those arrow keys are being used, or is it only the time between actual letter selections?

[Luke 42083]

It’s the time between letter inputs.