Revisions feeds load very, very slowly



4 years ago
4 years ago


(Reporter: sheppy, Unassigned)





4 years ago
The MDN RSS feeds for recent documents and recent revisions are both very slow, with the revisions feed not loading at all most of the time. The l10-updates feed is failing to load at least sometimes, too. This is troublesome, since the l10n teams use it to track what they need to update.

Recent documents feed: (loads but slowly)

Revisions feed: (times out essentially every time)

As has the feed of pages changed since they were last localized:

The new files feed works fine, though, or seems to:
Looks like this started when we did p2v on the MDN db servers in bug 1144314.

Adding :sheeri and :jakem
updated the configuration so the database buffer pool is now 6G in size, which is about half the size of the total database.
:groovecoder, can you update on steps taken to date?

In bug triage, anecdote suggests these steps did not resolve the issue yet.
Severity: normal → minor
Flags: needinfo?(lcrouch)
What :sheeri said in ... we increased memory to the DB server, so at least it stopped taking the site down.

Agree with the 'minor' severity for now, since the revision dashboard isn't affected by these queries. May need to bump the severity later if we start to see more problems that affect the rest of the site too.
Flags: needinfo?(lcrouch)
Are these feeds read-only? If so, they're great candidates to put on the read-only VIP. Right now the slave is a failover point and no queries are running against it, so by naming a new handler and using the read-only VIP you might be able to glean more performance.
They are read-only. We'll look at adding multi-db-router sometime so we can route reads to the slave db.
I've made some improvements to the SQL queries we use in bug 1169673 that should have made the revision feed a lot faster ~3 seconds. We still do some heavy content diffing when rendering the feed, but the LB should cache the response at least.
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.