Problem/Motivation

Selecting a comment prefetches every sibling comment, firing roughly one full fragment request per sibling. A single click on a wide thread fires ~9 independent uncached fragment requests, amplifying server load and competing with the user's own navigation.

Steps to reproduce

  • Open a node with 200+ comments under ACT.
  • Select a comment with many siblings.
  • Observe many full fragment requests fire in parallel, one per sibling.

Proposed resolution

  • Prefetch only a small window of adjacent siblings, or defer sibling prefetch until the sibling is revealed.
  • Keep the selected comment's own full-body load immediate.

Remaining tasks

  • Confirm selection still reveals replies promptly with the reduced prefetch.

User interface changes

None, beyond fewer background requests during selection.

API changes

None anticipated.

Data model changes

None anticipated.

Comments

freelock created an issue. See original summary.

  • freelock committed 6d0b6d0f on 1.0.x 
    test: #3622841 Count only the sibling-prefetch requests issued after...

  • freelock committed dcc90e18 on 1.0.x 
    fix: #3622841 Selecting a comment prefetches every sibling
freelock’s picture

freelock
Location Seattle
commented
Status: Active » Fixed

Fixed.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.