You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before we get too heavy into re-designing and tuning these components, we should have a way to measure that we are actually making things better, at least from a performance point of view.
React has recently introduced the Profiler api [link] as a way to get some insight into where our components are spending time, and when they re-render.
We can use this thread to discuss how we want to both measure and track our performance gains.
Do we want to just do performance testing in an adhoc manor, (ie, manually test before and after a set of changes), or do we want to try and bake performance tests into the travis build?
The text was updated successfully, but these errors were encountered:
Before we get too heavy into re-designing and tuning these components, we should have a way to measure that we are actually making things better, at least from a performance point of view.
React has recently introduced the
Profiler
api [link] as a way to get some insight into where our components are spending time, and when they re-render.Blog post introducing the api.
I also found the storybook-addon-performance which adds a performance tab to story book.
We can use this thread to discuss how we want to both measure and track our performance gains.
Do we want to just do performance testing in an adhoc manor, (ie, manually test before and after a set of changes), or do we want to try and bake performance tests into the travis build?
The text was updated successfully, but these errors were encountered: