Dear Maintainer,
With the update from libgoogle-perftools4 2.1 to 2.2.1 I saw a serious
performance regression in a benchmark which is sensitive to memory
allocation performance.
Runtime of the benchmark increased from less than 5 seconds to over
13 seconds (with glibc's allocator finishes the benchmark in 7s).
`perf report -s dso` show almost 2/3 of the cycles spent in
libtcmalloc.so.4.2.2 for the benchmark.
Compiling the debian source package on the host results in a libtcmalloc
which restores the performance and perf shows only 24% of the cycles for
the benchmark spent in libtcmalloc.
libtcmalloc-minimal4 has the same problem.