4 ms·
It's been a long time but from what I remember the selling point for EASTL is the ability to specify your own allocator instance for every container. EA writes
by zrail 5y ago
It's been a long time but from what I remember the selling point for EASTL is the ability to specify your own allocator instance for every container. EA writes portable code across lots of different architectures, many of which share a lot more with embedded systems than with PCs. They have constrained memory or special dedicated memory areas. Also, iirc EA uses tagging allocators extensively letting them trace against memory budgets down to the team level.
Edit: there's an extensive FAQ in the docs folder: https://github.com/electronicarts/EASTL/blob/master/doc/FAQ.md https://github.com/electronicarts/EASTL/blob/master/doc/FAQ....
- jeffbee 5y agoThe FAQ seems to answer the question of why EASTL is better than some extremely old and bad standard libraries, not why it is better than modern ones.
- tyingq 5y agoI don't know where they do their CI/CD now...they seemed to have moved off of travis. But, there's a snapshot of a benchmark from 2019 still here: https://github.com/electronicarts/EASTL/issues/267 https://github.com/electronicarts/EASTL/issues/267
- ThePadawan 5y agoThat was my impression of how EASTL came to be. Everybody used old and bad libraries, so they wrote ones that were better. Imagine they wrote their own Javascript engine before V8 became really performant. That sort of thing.
- fnord123 5y agoSpecifying your own allocator is like a main feature of bde from Bloomberg: https://github.com/bloomberg/bde https://github.com/bloomberg/bde
- maxlybbert 5y agoThat is accurate. That general model eventually made it into the standard, because of EA and Bloomberg ( https://en.cppreference.com/w/cpp/memory/memory_resource https://en.cppreference.com/w/cpp/memory/memory_resource ).