Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow generated bindings to use custom trace hooks #364
Labels
Comments
|
Fixed by #820. |
ChrisParis
pushed a commit
to ChrisParis/servo
that referenced
this issue
Sep 7, 2014
Remove obsolete copy of the ElementTraversal tests that now live under dom/nodes/.
glennw
pushed a commit
to glennw/servo
that referenced
this issue
Jan 16, 2017
Rewrite the alpha batcher to use a simple shortest-common-subsequence approximation algorithm. This makes the batcher simpler and more scalable and improves its output at the cost of a small constant overhead. Because of the scalability improvements, this patch lifts the cap on the number of alpha batches per render phase to 4. Before-and-after measurements on http://en.wikipedia.org/wiki/Servomechanism: * Draw calls: 161 → 77 (2.1x fewer) * Backend CPU time: 3.15ms → 3.32ms (5.4% slower) * CPU compositor time: 1.03ms → 0.53ms (94% faster) * GPU time: 1.83ms → 1.80ms (1.7% faster) Based on servo#364. r? @glennw <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/367) <!-- Reviewable:end -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Perhaps even require all generated bindings to provide one in a known location: dom::bindings::typename::trace, for instance. This will be necessary whenever Node eventually becomes generated, and we could use it for types like ClientRectList too (#363).