Profiling CEF

[pmadr]

I'd like to profile my code in CEF, but tutorial for profiling Chromium doesn't work.
-- https://chromium.googlesource.com/chrom ... g-on-Linux
No chrome-profile file is created.

So I tried callgrind. It works but profiles the complete run only.
I'd like to profile just parts of code. So I added CALLGRIND_START_INSTRUMENTATION, CALLGRIND_STOP_INSTRUMENTATION and CALLGRIND_DUMP_STATS on the wanted places but without any effect. CALLGRIND_TOGGLE_COLLECT doesn't work to.

Thank you for any help.

Note: I started to profile CEF because it seems that there is average 30% slowdown between Chromium versions 63 and 84.

[magreenblatt]

Most slowdowns in browser behavior are related to web content. I would suggest starting with the DevTools profiling tools, and continuing with the tracing tool if DevTools doesn't provide enough information. Make sure to use a fully optimized official release build for best performance.