Runtime and memory profiling from logs

[ivokwee]

We can profile startup time for different stages at startup and memory usage during startup from the log files. This enable us to compare different versions and different deployments. Below is an example for the master vs insertUI branch. What we need to do is insert in the stdout/stderr logs some timer start/stop points.

[ivokwee]

At the moment, I match some log output lines with start/stop and compute the lapsed time. See fig below. It would be easier to insert start/stop commands in the stderr/stdout log directly but to be able to profile older logs, this works.

[phisanti]

Which method did you use for the profiling?

I have also tried to do some profiling. To build the analysis, I used the profvis like this:

profvis({shiny::runApp('components/app/R')}, prof_output = 'profvis.html')

While running the app, I just loaded the example data a log out the app. This is what I got:

Clearly, most of the time is spent on generating the different boards, which is normal.