In the above example, the application called
at about the 22 sec mark. But the other, smaller pauses were inserted by the
, which temporarily pauses profiling when data generation rate exceeds data spill rate and it is about to lose data. The data is flushed and then the collection resumes. In the paused regions, your application is not executing: the
lets the application exhaust its current quanta and then prevents it from being scheduled on the CPU until all the data has been saved to a file.