We should make it possible to restore display of number of conditions used by filter on the filter's page. This is very useful for debugging filters (especially if they're hitting the condition limit, see T129171 and T132048). It was removed in rEABFafb78deb84e909459fd4e1b5228c4255e956bed6. To avoid performance issues, this would be gated by new config variable $wgAbuseFilterProfile, which would only be turned on temporarily when a wiki actually runs into the limit.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | matmarex | T132048 Change $wgAbuseFilterConditionLimit for wikimedia commons | |||
Resolved | matmarex | T132200 Enable $wgAbuseFilterProfile on Commons for a few days | |||
Resolved | matmarex | T132189 Restore display of number of conditions used by filter on the filter's page, gated by new config variable $wgAbuseFilterProfile |
Event Timeline
This is a duplicate but I can't seem to find it now. See also https://gerrit.wikimedia.org/r/#/c/201104/ (now very outdated) which attempts to fix this and comments at T101648
Hmm, interesting. I'll look at these patches. But I've already written some code, and I think my partial solution is going to be easier to get deployed soon (and I want to use it to debug some filters in production for T132048). Reverting https://gerrit.wikimedia.org/r/#/c/211951/ will also probably make it easier to rebase https://gerrit.wikimedia.org/r/#/c/201104/ :D
Change 282386 had a related patch set uploaded (by Bartosz Dziewoński):
Revert "Removed filter profiling using $wgMemc"
Change 282387 had a related patch set uploaded (by Bartosz Dziewoński):
Add $wgAbuseFilterProfile to enable filter profiling
Change 282387 merged by jenkins-bot:
Add $wgAbuseFilterProfile to enable filter profiling
The feature can now be re-enabled by setting $wgAbuseFilterProfile = true (documented at https://www.mediawiki.org/wiki/Extension:AbuseFilter). It's disabled by default (and for all Wikimedia wikis). The idea is that if a wiki runs into the condition limit, we can enable it for a while, optimize some expensive filters and disable it again – I'll be trying that for Commons per T132200.