Memory size get exhausted if we try to use this module in system which has 10,000+ users

Add limit with the query.

Same

I encountered this issue too, and the solution suggested in the #2 comment resolved it for me.

We should also fix it in Realname plugin. I don't like idea of hardcoding 50 items, we already have dropdownLimit option, we can pass it into ajax call and use it inside plugin.

Our site doesn't crash since we have a lot of memory available, it just takes a few minutes. A lot of resources wasted as the dropdown only shows a fraction of the results (defaults to 10). I also don't think it is a good idea to essentially export the entire user database for privacy reasons. So having at least a limit is a good start, I think 1000 is still way too much. Is there really a use-case for more than 100 results in a dropdown?

If you show 10 results, why not query for 10 results? just re-use that setting for the query limit.

Furthermore the limit should be configurable for the user with a useful default, eg. 10?

I think this is major.

Yea setting a hard limit here doesn't make much sense. Especially when we already got a "dropdownLimit" setting. Since this module uses AJAX to get the entities and the entity query does the filtering, we can simply use the "dropdownLimit" setting for the limiting.

I implemented this inside 📌 Allow to filter nodes by bundle Active , because that issue has a bunch of other code changes and I don't want to bother with rebase errors.

POSTPONED on 📌 Allow to filter nodes by bundle Active .

I see no reason to combine two issues into one, they are not related.

See my comment 📌 Allow to filter nodes by bundle Active . We should handle this in the same way.

Agreed, I'll start here once 📌 Allow to filter nodes by bundle Active is merged.

Note to myself, I already implemented this feature in https://git.drupalcode.org/issue/ckeditor_mentions-3544907/-/tree/941420.... I just have to use the plugin instead of hardcoding a url query parameter.

grevil → closed merge request !24

Ok, once the new plugin system is merged in 📌 Allow to filter nodes by bundle Active , this can be reviewed and merged as well.

POSTPONED on 📌 Allow to filter nodes by bundle Active .