 Okay, so welcome to the talk of provided calling. I'm going to show you something interesting because there are some people are asking for RC, if you'd like better to understand how to use the call. So that's why I'm going to do some demonstrations. So I see what to do, like everybody's got their own game to do, which is the error register, which makes a big difference. D, the program. Call B is one of the tools for the company to set up, define its profile, and what it basically does, it interprets the program. Yeah, it interprets the program. It basically tries to set the records, all it takes a little bit. So you can get something called. It records it, and it will give you a call graph and it will also give you a text. And there is a countercard, which is the tool to visualize it. So a small program which has functions, A and C, which just spends some time. Here you have function B, which goes more than nine times. And there you call one of the letters of real estate, one of the real estate letters. It will take 19% of the time. It will take just that person. So if we are on the tool and just have a little result, basically the visualization is mainly used. It moves from the view of the Cormie man interpretation. So this is the small function, which spends like four... You can't do that. You can't do that. So basically it wants cause you can see the visual representation. This is just a small part of the program. And here we have the views like this in the summary. This is the standard which is spending. This is the inclusive cost and how much time it's spending in the function and everything it costs. And here, just itself, it just spent in the function itself. So for example, here we can see that the vast majority of the program is in function C. And there are some functions here. Show you this program and it's percent. So we can see that that's basically like 90% of 10%. Just think we will, and we can see what cost each function. So for example, in the center, we can see that it's called from main. We can inspect the source code which also shows some information in the source code. Here's the source code for main and you can see that the vast majority of time spent in the main is called from C as well. Yeah, so this part of the life is like a summary of the skeleton stuff like we're just going to source code and inclusive this time which is spent in the function and it calls recursively. It calls an incident that's spent in the main and everything it calls which is basically usually the more inclusive time. The self-time is usually when you actually find something which won't improve life. If something has a bit inclusive time, it's self-time usually. Our option is maybe something is called some kind of sort of a kind of something called an inclusive time. It's often not just a simple tree sometimes a better person actually like you may have a function which in some conditions is made in the core here or this one sometimes may hold this for example the edge number the size of the status that you We have info for each role, but we have info for a million calls and we are trying to find out whether we can in order to make something call less. So we are trying to have inclusive calls, it's function. It needs to be improved because of this function, but this function needs to be improved because of this function. So if I like the functions, it should be improved each other, and it's going to be C, which is going to be number 2 and B. So this file, if it looks sometimes confusing, it's necessary to be caught. As I said, there is a cycle and you may be found making something many times more. It pops. Or maybe you just follow those words and it pops. If you want that, then start counts, stop counts, start counts. It's something important to look at. Profiling to separate your instrumentation account. Let's see where the most important ones are. They start with A, you can go down. In this case, I'm going to turn it off simply. We shall have shows again. This is just shows then, this is in parts. It's not just that they are more boring. We can see that there is a sweet list of listeners, which answers the name. And it describes when you start expensively screening formula. Instead of just asking. And your improvement is not as big as this shows. Because...