Profiling of BEAM simulation - CPU

[nikolayilyin]

We need to do a general profiling of CPU usage - in the ideal world BEAM should consume 100% CPU during all the simulation steps, but we are not able to achieve that so far. We need to understand where are the places of low CPU usage and why.

Probably the first step might be to analyze the cpu_ram_usage graph we have for all latest simulations made on AWS (for example - cpu_ram_usage.csv.gz) and understand at what time of beam log we have the most/the least of CPU usage. It would be great to do this analysis for many different simulations, preferably for the ones with multiple iterations. Because some of patterns might be related to some specific changes in the used code for each simulation.

The next step might be profiling of small simulations locally (beamville, sf-light) in order to understand better why there is low CPU usage.