Color for time - Githubissues

andywer / postcss-debug

Debug your postcss workflow with ease! Creates snapshots of your CSS files before/after each postcss plugin is run.

MIT License

95 stars 7 forks source link

Color for time #9

Open ai opened 8 years ago

ai commented 8 years ago

We should highligh plugin and file time in different colors — green for the fastest and red to the slowest

/cc @Gaserd

Gaserd commented 8 years ago

@ai Yeap 👍

andywer commented 8 years ago

True. I also thought about that, but there are some detail issues:

Do we color by

relative time (slowest/fastest for current file)
relative time (slowest/fastest for all files)
absolute time (let's say everything < 5ms is green, > 10ms is red, color gradient for 5ms < time < 10ms ) ?

I guess a good solution would have to consider all three metrics, but only show one combined color.

andywer commented 8 years ago

PS: I just had an idea. I don't know if it's good or rather not, so I will just post it here:

We could ask the user for permission once and then sent simple anonymized benchmark reports to some server to gather statistics about the most popular postcss plugins and their performance benchmarks.

Gaserd commented 8 years ago

@andywer I think relative time (slowest/fastest for current file) And collection statistics this good idea

ai commented 8 years ago

I think realtive time is fine too. Because the main purpose of coloring is to find slowest plugins and optimize them.

1j01 commented 7 years ago

There should probably be an absolute cutoff though, like less than 5 or 10 ms is always green, right?