Article <v4dtih$23kjq$2@dont-email.me>

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 <v4dtih$23kjq$2@dont-email.me>

Deutsch English Français Italiano

<v4dtih$23kjq$2@dont-email.me>

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

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: J Newman <jenniferkatenewman@gmail.com>
Newsgroups: comp.os.linux.misc
Subject: Re: Script to conditionally find and compress files recursively
Date: Thu, 13 Jun 2024 12:46:10 +0800
Organization: A noiseless patient Spider
Lines: 31
Message-ID: <v4dtih$23kjq$2@dont-email.me>
References: <v48s96$u6fg$1@dont-email.me>
 <v4b46s$7dh$1@tncsrv09.home.tnetconsulting.net>
 <wwvo7868waw.fsf@LkoBDZeT.terraraq.uk>
 <083d0e35-e02d-8668-726f-7aa89980e9b2@example.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 13 Jun 2024 06:46:10 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="d01cce3e8d98c9e911112d89133c53f3";
	logging-data="2216570"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18a8gk9aLxpG2/w/6qLAD6ReWJOXQFkNF6YYudxfeyeQw=="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:nlX7IFLkZVQgSbsSYglMFiBUQyU=
In-Reply-To: <083d0e35-e02d-8668-726f-7aa89980e9b2@example.net>
Content-Language: en-US
Bytes: 2454

On 12/06/2024 16:13, D wrote:
> 
> 
> On Wed, 12 Jun 2024, Richard Kettlewell wrote:
> 
>> Grant Taylor <gtaylor@tnetconsulting.net> writes:
>>> On 6/11/24 01:53, J Newman wrote:
>>>> Any suggestions on how to proceed?
>>>
>>> As others have said, it's very difficult to tell within the first five
>>> seconds what the ultimate compression ratio will be.
>>
>> Not just difficult but impossible in general: the input file could
>> change character in its second half, switching the overall result from
>> that that is (for example) a gzip win to an xz win.
>>
>>
> 
> This is true! The only thing I can imagine are parsing the file type, 
> and from that file type, drawing conclusions about the compressability 
> of the data, or doing a flawed statistical analysis, but as said, the 
> end could be vastly different from the start.

OK good point...as mentioned elsewhere my experience is with compressing 
video files with lzma.

But if we accept that the script will make mistakes sometimes in 
choosing the right algorithm for compression, do you suggest parsing the 
file type, or trying to compress each file for the first 5 seconds, as 
the option with the least errors in choosing the right compression 
algorithm?