-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
Many choices of conditions have been added to the edit search with not enough care about resource usage it involves. Edit search frequently pushes servers beyond alert's threshold and is often associated to (hopefully short) periods of unavailability for other users.
While there currently is an attempt to mitigate the issue with MBS-12731, it would only be a band-aid, but it would still allow users to bring the server down even though it's for a short time only.
For a better understanding of what is going on and to help with deciding on how to prevent unintentional abuses it would be very useful to know how many resources are used by each edit search condition in the worst-case scenario.
Just an idea up in the air but its relevancy depends on which profiles we'd find: It could possibly be used to weigh edit search conditions and only allow edit searches having a sufficient sum of inverted weights.
- is related to
-
MBS-12731 Preselect restricting edit search to the last 2 weeks
- Open