Re:Benchmarking C++ Allocators
by mehrdadn on Monday April 27, 2020 @10:41PM
(#23002769)
> In good dynamic language runtimes, for example
I'm talking about C++, not dynamic languages?
Are you talking about implementing a dynamic language in C++? Sure, do whatever you want in that case. Seems pretty fair to >99.9(9...?)% of developers aren't doing that.
I think it's safe to say dynamic language writing is to dynamic memory allocation as NASCAR is to car acceleration. You (should) already know your metrics will necessarily differ from most other people's.
Re:Benchmarking C++ Allocators
by saagarjha on Tuesday April 28, 2020 @03:24AM
(#23004409)
That was just an example of a place where fast path performance defined the runtime performance, as that’s how they become optimized. You can see a similar pattern when inserting keys into a hashmap, for example.
I'm talking about C++, not dynamic languages?
Are you talking about implementing a dynamic language in C++? Sure, do whatever you want in that case. Seems pretty fair to >99.9(9...?)% of developers aren't doing that.
I think it's safe to say dynamic language writing is to dynamic memory allocation as NASCAR is to car acceleration. You (should) already know your metrics will necessarily differ from most other people's.