Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <v4tuvf$1qto5$1@dont-email.me>
Deutsch   English   Français   Italiano  
<v4tuvf$1qto5$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!fu-berlin.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: davidd02@tpg.com.au (David Duffy)
Newsgroups: comp.lang.c,sci.stat.math
Subject: Re: realloc() - frequency, conditions, or experiences about relocation?
Date: Wed, 19 Jun 2024 06:48:17 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <v4tuvf$1qto5$1@dont-email.me>
References: <v4ojs8$gvji$1@dont-email.me> <875xu8vsen.fsf@bsb.me.uk> <v4ovqf$j5hq$1@dont-email.me> <87zfrjvqp6.fsf@bsb.me.uk> <v4pb4v$lhgk$1@dont-email.me> <20240617180249.96dfaafa89392827aa162434@g{oogle}mail.com>
Injection-Date: Wed, 19 Jun 2024 08:48:17 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="31d8f887133f0f81d700803c97977601";
	logging-data="1931013"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19y0qBGbwcBYZ9zEnccmGyzc2qWwMSSv8M="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-112-generic (x86_64))
Cancel-Lock: sha1:Ufn1u77c+t57vdkhPzXMhxcM/L8=
Bytes: 1992

In sci.stat.math Anton Shepelev <anton.txt@g{oogle}mail.com> wrote:
> [cross-posted to: ci.stat.math]
> 
> Malcolm McLean:
> 
>> We have a continuously growing buffer, and we want the
>> best strategy for reallocations as the stream of
>> characters comes at us. So, given we now how many
>> characters have arrived, can we predict how many will
>> arrive,
> 
> Do you mean in the next bunch, or in total (till the end of
> the buffer's lifetime)?
> 
Isn't this a halting problem?  Aren't the more important data: 
how much memory the user is allowed to allocate, the properties of
the current system's memory allocation algorithm, when your stream
will have to go to disc or other slow large volume storage, how
the stream can be compressed on the fly (the latter might well give
strong predictions for future storage requirements based on what 
has been read to date).