Spun off from T101648, it would be nice to be able to run and profile the filter for some given text (via a form). This could mention real time and conditions hit.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T185154: AbuseFilter (and dependencies): code stewardship review
T101648: Remove average run time and consumed conditions to make editing faster - Mentioned Here
- T132189: Restore display of number of conditions used by filter on the filter's page, gated by new config variable $wgAbuseFilterProfile
T101648: Remove average run time and consumed conditions to make editing faster
Event Timeline
Comment Actions
Boldly closing this. Right now, we have a much more efficient profiling than what we had in 2015. In fact, it's already been reenabled on a couple of wikis. Since on-demand profiling would require additional work, both in coding and for filter editors (which should remember to disable it), and also doesn't help identifying unsuspectably slow filters, I think that the existing profiling is a better and easier solution.
Of course, feel free to reopen if you think there is something that would be better accomplished with this solution.