While profiling ARROW-16161, Memory allocation would sometimes appear to take up a few percent of total runtime. Especially the creating/copying of CPUMemoryManager objects seems to be more costly then then allocator calls themselves at times. It would be good to see how much different operations are affected by this (possibly even distinguish between time a Pool allocation and in the allocator itself).
Reporter: Tobias Zagorni / @zagto
Note: This issue was originally created as ARROW-16712. Please see the migration documentation for further details.
While profiling ARROW-16161, Memory allocation would sometimes appear to take up a few percent of total runtime. Especially the creating/copying of CPUMemoryManager objects seems to be more costly then then allocator calls themselves at times. It would be good to see how much different operations are affected by this (possibly even distinguish between time a Pool allocation and in the allocator itself).
Reporter: Tobias Zagorni / @zagto
Note: This issue was originally created as ARROW-16712. Please see the migration documentation for further details.