[ENet-discuss] boost.pool & enet

Paul Du Bois paul.dubois at gmail.com
Sat Jul 22 13:23:30 PDT 2006


Only indirectly relevant, but I tried using boost pool about two years
back for another project and almost immediately ran into a leak and a
crash. I sent test cases and patches to the list but didn't have time
to follow up any further, and ended up using something handrolled.

You may want to set aside time to verify that it is as mature as the
rest of boost (or time to make it so :)

p

On 7/22/06, Zola <looseonthestreet at gmail.com> wrote:
> Hello,
>
> 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.
>
> A pool allocator might solve this problem.
> Has anyone tried, or been successful in using enet with the boost pool
> allocator?
> It can be found here:
> http://www.boost.org/libs/pool/doc/index.html
>
> As stated:
>
> "Pools are generally used when there is a lot of allocation and deallocation
> of small objects."
>
> "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."
>
> Has anyone had experiences with this combination of enet and pool
> allocators, or boost's pool?
> And, is enet suited to be plugged into such a system?
>
> - Zola
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
>


More information about the ENet-discuss mailing list