Closed Bug 1182627 Opened 9 years ago Closed 9 years ago

kuma.wiki.views:compare_revisions Render/wiki/compare_revisions.html spike

Categories

(developer.mozilla.org Graveyard :: Performance, defect)

Product:
developer.mozilla.org Graveyard
Component:
Performance
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1190171

People

(Reporter: groovecoder, Unassigned)

References

(
URL
)

Details

(Keywords: in-triage) 

The compare_revisions view can get a massive spike for some pages? Possibly when comparing across a large span of history for a page with many revisions?

Today there were 2 transaction traces, both for /en-US/docs/Interfaces$compare.

https://rpm.newrelic.com/accounts/263620/applications/3172075/transactions#id=5b225765625472616e73616374696f6e2f46756e6374696f6e2f6b756d612e77696b692e76696577733a636f6d706172655f7265766973696f6e73222c22225d
Adding to performance tracking bug.
Blocks: 1177264
Another 2 transaction traces for en-US/docs/Interfaces$compare earlier today.

All 4 were from Yahoo Slurp user agent. Maybe we should add some tags to prevent crawling compare views?
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/ebbc2eba6ab11aca7a92fd410ba237073ef0c63c
bug 1182627 - add nofollow to profile compare link

https://github.com/mozilla/kuma/commit/087f5017c34afd626a7de9ea81f0d7e1c3ed4b22
Merge pull request #3346 from mozilla/nofollow-compare-revisions-link-1182627

bug 1182627 - add nofollow to profile compare link

r=jezdez
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.