Last modified: 2014-11-17 09:21:08 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 T41326, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39326 - Query to get feedback for watchlisted pages performs poorly
Query to get feedback for watchlisted pages performs poorly
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ArticleFeedbackv5 (Other open bugs)
unspecified
All All
: Lowest normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks: 58956
  Show dependency treegraph
 
Reported: 2012-08-14 06:07 UTC by Asher Feldman
Modified: 2014-11-17 09:21 UTC (History)
4 users (show)

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


Attachments

Description Asher Feldman 2012-08-14 06:07:24 UTC
This query is regularly taking up to 8 seconds on enwiki and will worsen over time in current form.  The ORDER BY is satisfied by the af_relevance_sort_af_id index on aft_article_feedback, but that does nothing for any of the WHERE constraints on that table.  af_page_id would be the most reasonable to include in an index that can satisfy the ORDER BY.  That should help today but over time, a large number of rows will still have to be scanned for popular articles, so this needs a better long term solution.  A search engine would handle this much better. 

SELECT /* ArticleFeedbackv5Fetch::run */ af_id, af_net_helpfulness, af_relevance_sort, rating.aa_response_boolean AS yes_no FROM `aft_article_feedback` LEFT JOIN `aft_article_answer` `rating` ON ((rating.aa_feedback_id = af_id) AND rating.aa_field_id IN ('-1', '1', '16') ) LEFT JOIN `aft_article_answer` `comment` ON ((comment.aa_feedback_id = af_id) AND comment.aa_field_id IN ('-1', '2', '17') ) WHERE (af_is_deleted IS FALSE) AND (af_is_hidden IS FALSE) AND ((af_is_featured IS TRUE OR af_has_comment is true OR af_net_helpfulness > 0) AND af_relevance_score > -5) AND af_page_id = '5043734' AND (( af_form_id = 1 OR af_form_id = 6 )) ORDER BY af_relevance_sort ASC, af_id ASC LIMIT 51
Comment 1 Matthias Mullie 2013-05-09 13:16:28 UTC
Schema and indexes have changed and this should (for regular central/article feedback pages) be taken care of.

There's still a problem for feedback on watchlisted pages though. There are indexes with aft_page (the suggested af_page_id's equivalent in new schema), but the amount of watchlisted pages for some users is so high, it does not help much.

- I've changed the bug topic to more accurately reflex this watchlist issue.
- I've lowered the bug importance/severity. It _is_ a rather big deal, but not critical for now, as the watchlist has been disabled until we can come up with a solution.
Comment 2 Innocenti Maresin 2013-11-03 09:06:22 UTC
I guess, they’ll never come up with a solution. Special:ArticleFeedbackv5Watchlist was one of two things making the extension helpful for experts, the other being the “thumb down” button. The Foundation is not interested in extensions helpful for experts. It is interested in extensions helpful for crowds and the metapedianist mob.
Comment 3 Andre Klapper 2014-02-28 16:36:03 UTC
[Lowering priority to reflect reality, as AFTv5 is not very actively being worked on anymore.]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links