I added profiling markers for HTTP requests, JS execution, and
synchronous DOM parsing and took a look at some sites with known
pageload performance issues. The results have been... illuminating.
Besides clear inefficiencies that became noticeable (reading max 1kb
from HTTP response bodies at a
On Tue, May 3, 2016 at 12:16 AM, Paul Rouget wrote:
> This is awesome!
>
Great :)
I'm under the impression that it stops profiling after the page has
> loaded. Is that right?
>
It continues profiling from startup till shutdown.
___
dev-servo mail
This is awesome!
I'm under the impression that it stops profiling after the page has
loaded. Is that right?
On Thu, Apr 28, 2016 at 9:28 PM, Nick Fitzgerald
wrote:
> As of https://github.com/servo/servo/pull/10694, you can dump the profiling
> data from the `components/profile/time.rs` module as
As of https://github.com/servo/servo/pull/10694, you can dump the profiling
data from the `components/profile/time.rs` module as a timeline in a self
contained HTML file that is easy to share/upload/etc.
Usage:
$ ./mach run -r -p 5 --profiler-trace-path ~/output.html
https://reddit.com/
More
4 matches
Mail list logo