Minor but fun changes today
aland at deployingradius.com
Wed Feb 11 00:02:43 CET 2015
On Feb 10, 2015, at 5:41 PM, Matthew Newton <mcn4 at leicester.ac.uk> wrote:
> That makes sense - they're all hung off from each other anyway, so
> it should make cleaning up much easier as you don't need to worry
> about cleaning up each individual allocated block.
> My first computer had 32k memory…
Mine had 4K. :(
I spent a fair bit of time optimizing an embedded OS for an 8 bit CPU. Lots of fun… the same principles apply here. Don’t make it faster, make it do less.
> I thought talloc was generally slower (because of the management
> overhead). I guess the efficiencies come from a single malloc,
> rather than malloc/free all over the place when required. In my
> experience, malloc can be painfully slow.
Yes. The gain from using pools is MUCH more than the loss from the talloc() overhead.
More information about the Freeradius-Devel