THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The reason for using the itimer mode is based on the requirement of perf_events support in some scenarios within the container, which makes it compatible with such scenarios through the itimer. As described in the async-profiler troubleshooting section:
...
If changing the configuration is not possible, you may fall back to -e itimer profiling mode.
It is similar to CPU mode but does not require perf_events support. As a drawback, there will be no kernel stack traces.