With T101648 (June 2015) per-filter profiling was removed because it was slowing down the saving of edits. @dmaza did some fantastic investigation and it looks like since that time, the code was reworked so that the profiling happened //after// the edit was saved. This hopefully means we are safe to re-enable the profiling on wikis where it was removed, as this feature was hugely helpful and is sorely missed.
Relevant commit that deferred the profiling to after the edit was saved: rEABF43a538fe (April 2016)
We were thinking it might be better to first try turning on the profiling on a wiki smaller than enwiki,now have a [[ https://grafana.wikimedia.org/dashboard/db/mediawiki-abusefilter-profiling | Grafana dashboard ]] showing overall AbuseFilter runtimes, so we could perhaps use that to see if the per-filter profiling is slowing anything down. to ensure it indeed doesn't slow anything down noticeably.I thought the Portuguese Wikipedia would be a good one to start with, I thought the Portuguese Wikipedia would be a good exampleas it has a lot a filters and is big enough to provide meaningful data, which is still big enough to provide meaningful data butbut is not quite as risky as enwiki.