Hello,<br><br>I'm examining enet as a base of network code for a project which will have potentially hundreds of users in concentrated areas at certain times; I have one concern here- fragmentation, and the servers should be able to keep long-running uptimes. I forsee a barrage of tiny allocations and frees happening, and I'm concerned about fragmentation.
<br><br>A pool allocator might solve this problem.<br>Has anyone tried, or been successful in using enet with the boost pool allocator?<br>It can be found here: <a href="http://www.boost.org/libs/pool/doc/index.html">http://www.boost.org/libs/pool/doc/index.html
</a><br><br>As stated:<br><br>"Pools are generally used when there is a lot of allocation and
deallocation of small objects."<br><br>"Using Pools gives you more control over how memory is used in your
program. For example, you could have a situation where you want to
allocate a bunch of small objects at one point, and then reach a point
in your program where none of them are needed any more. Using pool
interfaces, you can choose to run their destructors or just drop them
off into oblivion; the pool interface will guarantee that there are no
system memory leaks."<br><br>Has anyone had experiences with this combination of enet and pool allocators, or boost's pool?<br>And, is enet suited to be plugged into such a system?<br><br>- Zola<br>