Last modified: 2013-08-14 16:19:50 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 T49723, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47723 - Cache action=credits results
Cache action=credits results
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.22.0
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks: 47722 46946
  Show dependency treegraph
 
Reported: 2013-04-26 11:04 UTC by Nemo
Modified: 2013-08-14 16:19 UTC (History)
3 users (show)

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


Attachments

Description Nemo 2013-04-26 11:04:08 UTC
1) May be the solution for bug 47722 (which blocks bug 47721).
2) Allows extensions and others to query the lists and include them where needed.

(Split from bug 27629 comment 13)
> [...] has for consequence that the collection
> extension
> might crash with a book of only 100 articles:
> https://bugzilla.wikimedia.org/show_bug.cgi?id=46946
Comment 1 Sam Reed (reedy) 2013-04-26 13:49:02 UTC
Not sure the DB is the correct place. As memcached is possible too
Comment 2 Kelson [Emmanuel Engelhart] 2013-04-27 18:18:38 UTC
@Sam

Memcached won't avoid to wait an eternity for the heavy edited pages... or do you think this is something which could be fixed (better SQL request)?
Comment 3 Andre Klapper 2013-05-29 12:24:30 UTC
Reedy: Could you answer comment 2 if you have time?
Comment 4 Andre Klapper 2013-08-14 16:10:14 UTC
Reedy: Could you answer comment 2 if you have time?
Comment 5 Tyler Romeo 2013-08-14 16:13:59 UTC
Has action=credits actually been profiled to determine what is causing it's low performance? Is it the actual DB query being executed that causes it to be slow, or is it the network transfer time required to deliver all that data plus the time requires to process and format it that is causing it to be slow?

In fact, other than "it is slow", what exactly do we even know about action=credits?
Comment 6 Nemo 2013-08-14 16:19:50 UTC
(In reply to comment #5)
> Has action=credits actually been profiled to determine what is causing it's
> low
> performance? Is it the actual DB query being executed that causes it to be
> slow, or is it the network transfer time required to deliver all that data
> plus
> the time requires to process and format it that is causing it to be slow?
> 
> In fact, other than "it is slow", what exactly do we even know about
> action=credits?

Nothing, for any reasonable definition of "we".

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


Navigation
Links