(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
Version: 1.22.0
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T40450 Reimplement MediaWiki's info action (tracking) | ||
| Open | Feature | None | T41533 Include action=credits output into action=info as well | ||
| Open | None | T87268 Copyright license and attribution issues (tracking) | |||
| Open | Feature | None | T30064 Collection extension needs some way to credit original authors of a work | ||
| Open | Feature | None | T49721 Restore action=credits on Wikimedia wikis | ||
| Duplicate | None | T49722 Make action=credits faster | |||
| Declined | None | T48946 Render server error for specific ZIM or PDF file | |||
| Open | Feature | None | T49723 Cache action=credits results |
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)?
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?
(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".