servo/webrender

Profile how primitive runs / clip nodes are being produced by Gecko

Open

#2,842 opened on Jun 25, 2018

View on GitHub
 (2 comments) (3 reactions) (0 assignees)Rust (319 forks)github user discovery
area: performancedifficulty: moderatehelp wantedpriority: soon

Repository metrics

Stars
 (3,355 stars)
PR merge metrics
 (PR metrics pending)

Description

It would be really interesting to profile a series of real world pages in Gecko, and get a sense of:

  • What the ratio of clip nodes is to primitives.
  • How many primitives (on average) there are per primitive run in a Picture.

From this information, we may be able to either:

  • Improve the display lists that Gecko is producing, if there are redundant clips (either in Gecko or in WR itself).
  • See if there is a better way to store some of this information given the real world usage patterns we see.

Contributor guide

Research direction
Set up a profiling environment for Gecko display list generation and collect data from several popular websites. Analyze the ratio of clip nodes to primitives and the average number of primitives per primitive run in pictures. Compare with Webrender's internal structures to identify optimization opportunities.
Tech stack
rust
Domain
computer graphics
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30