Re: Chunked mempools, a second verdict

On 5 May 2001, at 9:44, Adrian Chadd <adrian@creative.net.au> wrote:

> > then it should be kept as simple as possible. But it also tells that
> > there is lots of room for optimization in the code paths.. a average of
> > 125+ memory allocations per request is a lot of allocations.
>
> Robert and I are working on that in the newhttp branch.
> Hopefully that number will drop significantly.
>
> Remember that in src/store_client.c most storeClientCopy()s are
> done with a memAllocate(MEM_CLIENT_SOCK_BUF) to pass to
> clientSendMoreData()..

 try chunked pools ;) You'll see nice rates/sec for each pool. Most malloc
 traffic goes through HttpHeaderEntry, Short Strings, cbdata aclCheck_t.

> In either modio or commloops I played with a single temp buffer which
> was linked to the client state. This cut down on the mallocs a little,
> but quite a bit of the mallocing went to the strings on the client
> and server (and back? :-) side.

------------------------------------
 Andres Kroonmaa <andre@online.ee>
 CTO, Delfi Online
 Tel: 6501 731, Fax: 6501 708
 Pärnu mnt. 158, Tallinn,
 11317 Estonia
Received on Fri May 04 2001 - 20:44:38 MDT