Last modified: 2014-11-17 10:35:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20302, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 18302 - Display average runtime per filter to Special:AbuseFilter table
Display average runtime per filter to Special:AbuseFilter table
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 19435 (view as bug list)
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-04-01 15:15 UTC by Robert Rohde
Modified: 2014-11-17 10:35 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Robert Rohde 2009-04-01 15:15:16 UTC 
I think it would be useful for Special:Abusefilter to display the total time taken by running filters and for each row in the filter table to note its execution time.  In the current situation, with timing info only appearing on the rule page, it is hard to identify slow/poorly written filters without opening each one.
Comment 1 Andrew Garrett 2009-06-03 15:22:06 UTC 
Without modifying the TablePager infrastructure, this wouldn't be sortable, and is annoying to implement in any case.
Comment 2 Mike.lifeguard 2009-06-29 23:50:52 UTC 
*** Bug 19435 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Garrett 2009-07-16 16:47:50 UTC 
Marking this bug as Lowest priority.

I've done this in a batch to (usually enhancement request) bugs where:
* It is not clear that this bug should be fixed.
* It is not clear how to fix this bug.
* There are difficulties or complications in fixing this bug, which are not justified by the importance of the bug.
* This is an extremely minor bug that could not be fixed in a few lines of code.

If you're interested in having one of these bugs fixed, your best bet is to write the patch yourself.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links