I have a question regarding the example in 10. Rendered At.
Are those seconds, 2.2s, 3.0s, and 3.6s above the time when you typed 123 for password since you started profiling?
and each corresponding milliseconds, 2.3ms, 1.4ms, and 2.1ms represent time it took to render the component?
That's right. I've briefly mentioned it in the post under the same heading.
2.2s, 3.0s, 3.6s denote the linear time at which the re-rendering completed since the start of the profiling session. And the 2.3ms, 1.4ms and 2.1ms denote how long it took for each re-render.
This was very nice post, Dinesh~
I have a question regarding the example in
10. Rendered At.Are those seconds,
2.2s,3.0s, and3.6sabove the time when you typed123for password since you started profiling?and each corresponding milliseconds,
2.3ms,1.4ms, and2.1msrepresent time it took to render the component?That's right. I've briefly mentioned it in the post under the same heading.
2.2s, 3.0s, 3.6s denote the linear time at which the re-rendering completed since the start of the profiling session. And the 2.3ms, 1.4ms and 2.1ms denote how long it took for each re-render.
Thank you, Dinesh.
Now I dig the new React Dev Tools