It's not % each section is called, it's % each section is taking up in the overall execution time.
See if you can find a tree view for the performance details. That tells you callstacks, which is useful if all the time is in a vector add method and you need to know what's calling it.
Usually there's like 90% of the program running time in like 10% of the code. Identifying what's running slow is the first step in fixing it. Maybe it's something that's easy to fix. Maybe it's something that's hard. Either way, you won't know if you don't look.
Yes, profilers are a bit scary to figure out, but if I could figure out how to use a version of VTune from 8 years ago to profile Darwinbots you can use a profiler too.