I noticed a large profiler overhead in https://share.firefox.dev/3PRC02T while profiling a speedometer 3 workload.

From this profile, mozilla::MarkerThreadId::CurrentThread seems to be very visible especially (in addition to the usual suspects around capturing a backtrace in a buffer).

According to padenot, we should look at using pthread_self instead of gettid (that does a syscall):

syscall(SYS_gettid) -- took: 513.187 ms [0.513187us per iteration]
pthread_self -- took: 0 ms [0us per iteration]
11044057845185138688
getttid -- took: 504.234 ms [0.504234us per iteration]
11044058531219138688

See also bug 1721569 which has some prior thoughts on this.

The severity field is not set for this bug.
:canova, could you have a look please?

For more information, please visit BugBot documentation.