News for hackers. Stuff that matters.

A comment on Benchmarking C++ Allocators. Parent comment

Re:Benchmarking C++ Allocators by w0utert on Tuesday April 28, 2020 @05:12AM (#23005152)
>> My data says that perf of malloc/free in actual programs (not fake ass shit calling malloc in a loop) is never affected by the call overhead.

I have thought the same for a long time until I ran some benchmarks on some of our 3D modeling code that uses Open CASCADE, and found out that in some cases allocation overhead was over 20% of total time spent in the CAD kernel...

[ Parent | on HN ]
Re:Benchmarking C++ Allocators by alexhutcheson on Tuesday April 28, 2020 @06:50AM (#23005689)
pizlonator is saying that the overhead of the function call itself (the “call” instruction itself) doesn’t matter relative to the body of that function. The body of the function still matters a lot.
[ Parent | on HN ]