Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: J Newman Newsgroups: comp.os.linux.misc Subject: Re: Script to conditionally find and compress files recursively Date: Thu, 13 Jun 2024 12:43:43 +0800 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Thu, 13 Jun 2024 06:43:42 +0200 (CEST) Injection-Info: dont-email.me; posting-host="d01cce3e8d98c9e911112d89133c53f3"; logging-data="2216570"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/0MLn+HayXMQBKbJB+nz83T42H1euwvN5+liNmKSoEQ==" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:OdSNP3yqHaGSejLLHbdMcKzM45Q= In-Reply-To: Content-Language: en-US Bytes: 1926 On 12/06/2024 11:21, Grant Taylor wrote: > 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. > > If you have the disk space, compress using all of the compression > options and then remove all but the smallest file. > > Then go on to the next file. > > > It's true that you cannot tell within the first 5 seconds what the ultimate compression ratio will be, but it seems to me (from compressing avi/mp4/mov files with lzma -9evv) that you can tell within +/- 5% to a high degree of confidence, what the ultimate compression ratio will be given the first 5 seconds.