-
Bug
-
Resolution: Fixed
-
High
-
5.6, 5.7, 5.8, 5.9, 6.0, 5.10
-
Severity 3 - Minor
-
We have made several improvements to the performance of @mentions in large instances, over a couple of versions:
Confluence 6.0.7
Mentions Plugin 2.1.7
- Don't search if the search string is the same as the last search
- Wait up to 1s for the user to type extra characters, or search every 3 characters (this prevents searches being run on every character while the user is still typing)
- Stop searching if 0 matches are returned on a search string, unless the string no longer contains the previous string (ie stop searching if we have found no results and the user keeps typing)
Confluence 6.1.1
Mentions Plugin 2.1.8
- All of the above fixes
- If three searches are submitted but the server has not yet returned any results, do not submit new searches until the server responds. This can stop too many searches being run against an instance which is having performance problems.
- duplicates
-
-
- Closed
-
- is related to
-
-
- Closed
-
![[Confluence] Page](https://bulldogwiki.internal.atlassian.com/wiki/images/icons/favicon.png "[Confluence] Page"){kind=icon}
(2 mentioned in)
[CONFSERVER-51906] Performance improvements to @mentions
A fix for this issue is now available for Confluence Server customers.
Upgrade now or check out the Release Notes to see what other issues are resolved.
A fix for this issue is now available for Confluence Server customers.
Upgrade now or check out the Release Notes to see what other issues are resolved.
We are having some performance issues in a Jira instance with ~10.000 users in the projects whose visibility is restricted to only a little group of users (~20 users). Do you know if some fix is planned for Jira Server?