bde

I don't, and I also haven't learned Rust. My experience with arena allocators comes from Bloomberg's C++ libraries[1]. For example, here's the documentation[2] for a thread safe heterogeneous allocator and header[3] for the underlying thread safe pool. It uses a mutex, but at a glance only when it needs to consult the fallback allocator (which could involve a system call). If you knew that the fallback allocator were a pre-allocated arena, maybe you could do with atomics only. The free list is already lock-free, and so too could be the block list. [1]: https://github.com/bloomberg/bde/wiki/BDE-Allocator-model [2]: https://bloomberg.github.io/bde-resources/doxygen/bde_api_pr... [3]: https://bloomberg.github.io/bde-resources/doxygen/bde_api_pr...

Hi, one of the authors here. BlazingMQ depends on two other open source C++ libraries: https://github.com/bloomberg/bde and https://github.com/bloomberg/ntf-core. I believe documentation writer wanted to highlight that BlazingMQ does not depend on frameworks like ZooKeeper, etc.

I like this topic, so here are some more "bit hacks" links, from my collection: * http://aggregate.org/MAGIC/ * http://graphics.stanford.edu/~seander/bithacks.html * https://stackoverflow.com/questions/109023/how-to-count-the-number-of-set-bits-in-… * https://github.com/bloomberg/bde/blob/main/groups/bdl/bdlb/bdlb_bitutil.h

Specifying your own allocator is like a main feature of bde from Bloomberg: https://github.com/bloomberg/bde

Yes... check out this repo: https://github.com/bloomberg/bde, a very powerful library developed by Bloomberg. A random example: https://bloomberg.github.io/bde-resources/doxygen/bde_api_pr...

Bloomberg has also developed a drop in replacement for std::string with SSO, and has a very well documented header file. https://github.com/bloomberg/bde/blob/master/groups/bsl/bsls...

with respect to the C++ Language: there was a book published in 1996. Large-Scale C++ Software Design by John Lakos. He's about to publish the second edition of the book while also expanding it's reach to span two volumes. Anyhow, while we await the publication of that book, John has been working at bloomberg. some of the code written there has been published to github[1]. He's also done a five hour lecture series [2] available on safari-online (paid service) that cover the topics of his book, and introduce the open source bloomberg repo as an example of code written in that style. I can't offer you a review as I've just found this all myself, but I'll be eagerly studying it along with some of the other items mentioned here. [1] https://github.com/bloomberg/bde [2]https://www.safaribooksonline.com/videos/large-scale-c-livel...

Similarly, Bloomberg's bsl::string (std::string) performs SSO as well and is used throughout Bloomberg's stack. https://github.com/bloomberg/bde/blob/master/groups/bsl/bsls...

Looks like the URL was updated: https://github.com/bloomberg/bde/wiki/BDE-3.0---Open-Source-...

It's a lot of C++ today. In fact, they have open-sourced a lot of the in-house tools they use, eg bde: https://github.com/bloomberg/bde

The allocators that appeared in the first C++ Standard were designed by the Committee and turned out to not be as useful as expected. Both Electronic Arts ( http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n227... , https://github.com/paulhodge/EASTL/ ) and Bloomberg ( http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n185... , https://github.com/bloomberg/bde ) proposed a different approach, which allow what you want. C++11 includes stateful allocators and scoped allocators.

I am not a huge fan of NIH but more often than not it is simply easier in the long run to roll something in house that does the job. Although the debt that piles up tends to dwarf the original choice it is often still a better idea due to having employee churn. Its much easier to keep it within the standards of normal coding conventions. I don't work at FB but near the bottom in the comments you can see that they build on existing C++ libraries that have been tried/tested. We do the [same thing][1] with smaller services simply because its easier in the SDLC process to move libraries that are already in-house. [1]: https://github.com/bloomberg/bde/tree/master/groups/bsl