From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Suppressing native compilation (short and long term) Date: Tue, 04 Oct 2022 09:57:21 +0300 Message-ID: <83lepwvzxq.fsf@gnu.org> References: <87bkqxf1ij.fsf@tethera.net> <8335c9dkyf.fsf@gnu.org> <83tu4odez7.fsf@gnu.org> <871qrrpkgx.fsf@trouble.defaultvalue.org> <834jwnbi6c.fsf@gnu.org> <87mtafnun5.fsf@trouble.defaultvalue.org> <83sfk6ahty.fsf@gnu.org> <87v8p1aiof.fsf@melete.silentflame.com> <87v8p01lbu.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36313"; mail-complaints-to="usenet@ciao.gmane.io" Cc: spwhitton@spwhitton.name, rlb@defaultvalue.org, monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org, akrl@sdf.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 04 09:25:30 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ofcIy-0009FA-VP for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 09:25:29 +0200 Original-Received: from localhost ([::1]:43902 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofcIx-0001YH-Nt for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 03:25:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52032) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofbsA-0003aO-UO for emacs-devel@gnu.org; Tue, 04 Oct 2022 02:57:47 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60558) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofbs9-0007V2-HZ; Tue, 04 Oct 2022 02:57:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=V7Pjvzu0Dlaez5GhZNKNuqp7YzYT8VyuM4WNYANhoFg=; b=R3LW9MVUz9ut Da0EOccerhsQVor/r6H87DGX9Fng9p575aAIbeIBjp+tYmMdmPDf1x9d4iUMeh7JB5cHadD6vCkzn 0mbXnCXx5KXC+RlRmsxvFH38ApAo9jMe/qKugfECOEazKhHJLYExXhaLEJ7fSsj/jgQaRaXiLEK5K xIQog9BP2KyrgXIQwUieaYdz1CJX71ajYcnwG2jLFS/vAV4X7PfWudKHBKemquqofnSAMHuNYgIC2 zxKWKlJuXXFk6DtV6Hvl1XYI5FV9FBIEQnefDScqa4NfYCAJ7ZUDxVsOHdMiMdE/3uIkvfuCFc3kX v8xh8SSARPn7LLRRZvn04w==; Original-Received: from [87.69.77.57] (port=3171 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofbrq-0004b3-5H; Tue, 04 Oct 2022 02:57:40 -0400 In-Reply-To: <87v8p01lbu.fsf@yahoo.com> (message from Po Lu on Tue, 04 Oct 2022 08:31:01 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:296846 Archived-At: > From: Po Lu > Cc: Eli Zaretskii , Rob Browning , > monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org, > akrl@sdf.org > Date: Tue, 04 Oct 2022 08:31:01 +0800 > > Sean Whitton writes: > > > The point with battery consumption is not about running vs. standby. > > The issue is that while users expect that running apt-get will drain the > > battery, they expect that once apt-get is done, the only battery-hungry > > processes are ones they start themselves. Laptop users typically avoid > > running apt-get without mains power plugged in. If I do an 'apt-get > > upgrade' then afterwards my CPU will be churning away compiling addon > > packages, so I can't just unplug. > > I don't know if that's true with Debian users, but nobody I know of > objects to running "dnf install" on battery. After all, installing new > packages only takes a short amount of time, certainly not enough to > significantly affect battery usage. > > OTOH, async native compilation is something I would definitely plug in > for. Why the difference, I wonder? Async native compilation also takes a short amount of time, as the data I posted indicates.