-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Optimization of HTML generated by cargo timings #13299
Copy link
Copy link
Closed
Labels
A-timingsArea: timingsArea: timingsC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`PerformanceGotta go fast!Gotta go fast!S-needs-designStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.
Description
Metadata
Metadata
Assignees
Labels
A-timingsArea: timingsArea: timingsC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`PerformanceGotta go fast!Gotta go fast!S-needs-designStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
Sometimes I use
cargo timingsin my projects, and find that the HTML generated by them often slows down the browser (chrome in my case).I have also measured the
cargo timingsin the cargo project for reproduce, and it seems to be taking longer to work as well. (As shown in the attached image, it took about 5s to become operational.)I guess that the browser is slowing down because the JS that is drawing the canvas is occupying the CPU.
There might be room for optimization of the generated JS.
cargo-timing.html.zip
Proposed Solution
No response
Notes
I didn't try this in Firefox because of #8850 .