people who care about latency often write their own allocators, and often do allocation/de-allocation very differently. e.g. arenas and temporary-vs-permanent storage; plus there are opportunities to take advantage of hardware & OS-specific features.
-
-
-
projects that plan for these things up front have been known to avoid: - ever using malloc() - memory fragmentation - de-allocations that cost more than a decrement instruction
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.