From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ca9eef4d5e2078ea
X-Google-Attributes: gid103376,public
From: Mats Weber <Mats.Weber@elca-matrix.ch>
Subject: Re: Beware: Rep spec on an enumeration type causes code explosion
Date: 1997/12/08
Message-ID: <348C4C76.31552A47@elca-matrix.ch>#1/1
X-Deja-AN: 296350141
References: <gwinn-0512972303070001@dh5055063.res.ray.com>
 <EKrsrr.LD7.0.-s@inmet.camb.inmet.com>
 <gwinn-0812971210080001@dh5055133.res.ray.com>
Reply-To: Mats.Weber@elca-matrix.ch
Organization: ELCA Matrix SA
Newsgroups: comp.lang.ada
Date: 1997-12-08T00:00:00+00:00
List-Id: <comp.lang.ada>


Joe Gwinn wrote:

> Historically, we have found that the only approach that always works, even
> when the system is straining under the load, is a fixed-block allocator
> offering three or four project-specific sizes of block.

We have found that allocating only sizes that are powers of two works well.
You need very few lists of free blocks and the implementation is very simple.
If you want to waste less storage, you can also use powers of a smaller
number, e.g. 1.5.