Make taxonomy views filter handlers more scalabale

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Since there's been no follow up in 3 months going to close out, if still a valid task please re-open

Thanks all!

This is almost certainly still an issue.

OK, there are several things this could mean since "handler" covers a lot of ground in Views, and even people on the issue seem to be referring to different types of handlers (relationship handler, filter handler, etc.). It could mean:

1. Optimizing the DB queries for the relationship or field handlers etc. (see also: taxonomy index table versus generic entity relationships).
2. Optimizing the exposed filter selector: In 11.x, you have a choice between a select dropdown and an autocomplete. Sites that expose th filter for a large view should obviously use the autocomplete. It would be a feature request to add support for the field widget that automatically switches between select and autocomplete (is that still a thing?).
3. Something pertaining to some multilingual handler used on the content translation view? Since the original issue was adding multilingual support.
4. Any number of other things.

Unfortunately, the original issue was a refactoring of the whole of taxonomy entity properties, so it could refer to any number of views. The taxonomy term listing view did receive any number of critical bug fixes during and after the D8 cycle, so if the issue was referring to that view, it might indeed be a duplicate of something fixed.

I spun up an 11.x site, installed standard with devel, enabled content translation, generated a bunch of articles and terms, and added various taxonomy handlers to various views. I was unable to distinguish any performance issues from the background noise of a quick-start site's inherent non-performant nature. :D

So I agree with outdated in the absence of a more specific bug report or feature request.