3 ms·
The best allocator for this kind of problem would of course be a compacting GC. First it would be much faster, it would be safer, and easier to use. For my big
by rurban 6y ago
The best allocator for this kind of problem would of course be a compacting GC. First it would be much faster, it would be safer, and easier to use.
For my bigger libraries glibc malloc and free has insane runtimes. Eg a final free could last over 1 minute. If you see this with a GC you would throw it out immediately. But apparently people don't measure and spread false rumors about GC's. Even a very poor and primitive GC as in emacs is not that slow as glibc malloc/free. A good one is miles faster. My GC has an upper limit of 10ms, not minutes.