🚀 go-pugleaf

In article <4jr71q$h66@solutions.solon.com>, stanr@tiac.net (Stan Ryckman) writes:

|> >Better yet: unless memory is really tight, have it double the size.

|> Not necessarily better.  If you're at 40% of your machine's
|> physical memory, doubling could be a real performance killer.

40% * 2 = 80% < 1, so 40% is kind of a bad choice for an example :)

|> With my suggestion (add some amount to the size and realloc)
|> you will rapidly reach the max if the sizes arrive "randomly".

I'd like to point out that the
worst case behavior with linear increases is O (n) mallocs and O (n**2) copies,
where n is the maximum size of blocks encountered;
with doubling, it is O (ld n) mallocs and O (n) copies.

|> Any strategy here would involve knowing something about your
|> target system, I think, [...]

Konrad Schwarz