5 ms·
That's what custom allocators in C++ are for. If your available memory is less than five times the working-set size, GC is less efficient than some sort of mal
by bitwize 15y ago
That's what custom allocators in C++ are for.
If your available memory is less than five times the working-set size, GC is less efficient than some sort of malloc/free perhaps with reference counting
- dpark 15y agoWhere did you get this 5x number? As for reference counting, that's rather time-expensive, and does horrible things to the cache in multi-threaded scenarios.
- bitwize 15y agoHertz and Berger's "Quantifying the Performance of Garbage Collection vs. Explicit Memory Management": http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.61.9682 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.61.9... The reference counting would only be used in certain cases where the dynamic extent of the object is unknown. Most objects can be cleaned up with an implicit management scheme like the RAII pattern in C++.
- dpark 15y agoThanks. I'll take a look at that.