Last modified: 2014-04-14 17:44:10 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 T65249, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63249 - Uncacheable RecentChanges feed, outlier in frontend cache misses
Uncacheable RecentChanges feed, outlier in frontend cache misses
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Highest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-29 02:45 UTC by Faidon Liambotis
Modified: 2014-04-14 17:44 UTC (History)
5 users (show)

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


Attachments

Description Faidon Liambotis 2014-03-29 02:45:26 UTC
On text Varnishes the misses list shows this URL: 
/w/api.php?hidebots=1&days=7&limit=50&hidewikidata=1&action=feedrecentchanges&feedformat=atom
as an outlier, with receiving approx 1700 req/min right now. For reference, the second on that list (also an outlier, probably a bug) is receiving 70 req/min.

From the headers, I see that it's all Cache-Control: private, expires immediately.

I have no data on when this began and it could be old, but I don't remember seeing it before. From the git logs I see commit I06ee0f01d896bc66545a1800b24693ce7524e433 (ChangesListSpecialPage: Separate all functionality for generating feeds) that changed some feed internals and URLs, so perhaps this is related?
Comment 1 Bawolff (Brian Wolff) 2014-03-29 03:47:29 UTC
> 
> I have no data on when this began and it could be old, but I don't remember
> seeing it before. From the git logs I see commit
> I06ee0f01d896bc66545a1800b24693ce7524e433 (ChangesListSpecialPage: Separate
> all functionality for generating feeds) that changed some feed internals and
> URLs, so perhaps this is related?

Yes, it appears that change disabled varnish cache, where previously it was set to cache in varnish for 10 seconds. Given the amount of hits that page gets, even a 10 second cache is probably helpful.
Comment 2 Gerrit Notification Bot 2014-03-29 04:32:07 UTC
Change 121912 had a related patch set uploaded by Brian Wolff:
Cache RecentChanges Atom feed in varnish for 15 seconds

https://gerrit.wikimedia.org/r/121912
Comment 3 Gerrit Notification Bot 2014-04-14 12:56:54 UTC
Change 121912 merged by jenkins-bot:
Cache RecentChanges Atom feed in varnish for 15 seconds

https://gerrit.wikimedia.org/r/121912
Comment 4 Gerrit Notification Bot 2014-04-14 12:59:39 UTC
Change 125714 had a related patch set uploaded by Reedy:
Cache RecentChanges Atom feed in varnish for 15 seconds

https://gerrit.wikimedia.org/r/125714
Comment 5 Gerrit Notification Bot 2014-04-14 13:00:35 UTC
Change 125716 had a related patch set uploaded by Reedy:
Cache RecentChanges Atom feed in varnish for 15 seconds

https://gerrit.wikimedia.org/r/125716
Comment 6 Gerrit Notification Bot 2014-04-14 13:19:11 UTC
Change 125714 merged by Reedy:
Cache RecentChanges Atom feed in varnish for 15 seconds

https://gerrit.wikimedia.org/r/125714
Comment 7 Gerrit Notification Bot 2014-04-14 13:19:24 UTC
Change 125716 merged by Reedy:
Cache RecentChanges Atom feed in varnish for 15 seconds

https://gerrit.wikimedia.org/r/125716

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


Navigation
Links