🚀 go-pugleaf

In article <4jq1o1$a8v@solutions.solon.com> msb@sq.com writes:

|> > > The realloc can certainly do something like use sz+10000
|> > > to "grow" the tmp area in tunable chunks, depending on the application.
|> > 
|> > Better yet: unless memory is really tight, have it double the size.
|> > This will set a fairly reasonable upper bound on the number of reallocs
|> > you will have to do.

|> Better yet: change "unless memory is really tight" to "if memory is
|> plentiful".  The doubling method can run out of memory when the amount
|> available is almost twice the amount that you need, not even considering
|> the possibility of fragmentation.

I guess it depends on the definition of `really tight'.  Now that most
machines have virtual memory, I tend to only consider two situations:
`memory is really tight' (no virtual memory) or `memory is plentiful'
(virtual memory).

You're right, of course, in that it is one aspect to consider.  (I
suppose you could also add code that when doubling failed, you tried 1.5
times, then 1.25, then...:-)
-- 
James Kanze           (+33) 88 14 49 00          email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs Bourgeois, 67000 Strasbourg, France
Conseils en informatique industrielle --
                            -- Beratung in industrieller Datenverarbeitung