Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>All I read about boost pool is: don't use it at all. The library is rather old (in boost 1.54 all files have copyright 2000 and 2001 except pool_alloc.hpp, which was edited in 2010) You can look <a href="http://bytes.com/topic/c/answers/819883-whats-boost-pool-allocator-good" rel="nofollow">here</a> for an question about performance (look for the answer of James Kanze). If you want only to use boost, I would suggest to use another library. If you need a custom allocator, do benchmarks. </p> <p><em>Edit:</em></p> <p>From <a href="http://www.boost.org/doc/libs/1_54_0/libs/pool/doc/html/boost_pool/pool/introduction.html#boost_pool.pool.introduction.when_should_i_use_pool_" rel="nofollow">Pools docu</a>:</p> <blockquote> <p>In general, use Pools when you need a more efficient way to do unusual memory control. </p> </blockquote> <p>So the qustion is what exactly is unusual memory control? Does it meet your special need to memory? <a href="http://erdani.com/" rel="nofollow">Andrei Alexandrescu</a> has written in "Modern C++ Design" about memory allocation and that there may be very different requirements depending on allocation <strong>and</strong> deallocation patterns. But according to this <a href="http://erdani.com/publications/cuj-2005-12.pdf" rel="nofollow">paper</a> he isn't convinced it was a very good chapter. </p> <p>So for me the final question is wether pool is better than std::allocator for the problems memory management? You have to messure it. Even with litle logic implemented in pool there might be more efficient algorithms for memory management used in your implementation. By the way one of the bugs of pool is <a href="https://svn.boost.org/trac/boost/ticket/7085" rel="nofollow">"Boost pool library it not header only as claimed in documentation"</a>. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload