paper-elements icon indicating copy to clipboard operation
paper-elements copied to clipboard

Measuring element perf "cost"

Open samccone opened this issue 10 years ago • 1 comments

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!) :sparkles:

Thanks :exclamation:


cc @ebidel @notwaldorf @cdata @tjsavage

samccone avatar Oct 21 '15 02:10 samccone

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

addyosmani avatar Oct 21 '15 09:10 addyosmani