Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Measuring element perf "cost" #50

Open
samccone opened this issue Oct 21, 2015 · 1 comment
Open

Measuring element perf "cost" #50

samccone opened this issue Oct 21, 2015 · 1 comment
Assignees

Comments

@samccone
Copy link

There has been much work recently around optimizing paper element elements, from dynamically creating ripple events, to removing styles, and much more.

I would love to come up with a list of measurable metrics that we want benchmark against. I know that using the debugger is super useful to find what is eating up a bunch of time locally, however at a "framework" or component level doing reproducible verifiable perf work is really really really hard.

From this list, I can then do some work around creating a tool that we can run on CI to give us some hard numbers for every single element.

the initial metrics that I am thinking would be....

  1. GC thrashing
  2. event listeners
  3. node count

(your ideas here!) ✨

Thanks ❗


cc @ebidel @notwaldorf @cdata @tjsavage

@addyosmani
Copy link

Would it be useful for this work to look at per-element first paint times too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants