How to use the React Profiler to find and fix Performance Problems

dasfsdf asdf asdf asdf asdf sdfasdfasdf asd fasdf Okay, I can certainly do that. Previously, I asked if you'd like to explore specific optimization techniques for React applications, or if you were interested in learning more about how to interpret the various charts and data that the React Profiler presents. Would either of those topics be helpful to discuss further, or is there something else about the React Profiler or performance optimization you're curious about? I'm going to switch this on and I'm gonna hit stop. And so now we can see a breakdown of stuff. We can see here. there's a small bump here, took 30 milliseconds. You can click, this took 38 milliseconds. We can see in general we have brought down the load time quite a bit. And this one is being the largest right now. So we can see now we're memorizing this cocktail list. Looks like it only rear-ended once, which is awesome. And so this cocktail browser took a total of 40 milliseconds now. so we really brought it down so we can crack down into each of these individual components and continue to kind of just recursively take a look at them and see if we can them to render less or to take less time. So we can see now these are rendering a total of five times. Think each you know each commit is gonna have a different number of renders. but this cocktail filter is another one that's rerender. So this, this is another one, which it's not really needing to re-render. So we can go into cocktail