Application Startup Profiling

While profiling an application startup by using async-profiling as an agent there's still the missing bit of info re measuring the runtime bootstrap till agent loading complete; I see this one as an interesting feature to be implemented together with the "classify" one i.e. marking as "bootstraps" the native-only stack-traces of the JVM before "jattach" is available. I have no idea if it's possible to implement something like that given the current architecture of the profiler, but it would be of great help for applications that need to be restarted/scale-up frequently, providing additional useful informations re hidden and still important costs (compiler threads startup cost, GC threads startup cost, initialization of GC data-structures and/or pre-touch costs, etc etc).

Obviously this means that it cannot be used as an agent anymore :)