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.bugs Subject: bug#44674: 28.0.50; Adding current-cpu-time for performance tests Date: Mon, 16 Nov 2020 21:22:47 +0200 Message-ID: <83eektrtrs.fsf@gnu.org> References: <83y2j1rz2f.fsf@gnu.org> <83sg99ryla.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23922"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mattiase@acm.org, p.stephani2@gmail.com, 44674@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Nov 16 20:35:37 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1kekHl-0005x7-Gi for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 16 Nov 2020 20:35:33 +0100 Original-Received: from localhost ([::1]:33494 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kekHk-0002Oc-EU for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 16 Nov 2020 14:35:32 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50120) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kek6d-0006Ay-2t for bug-gnu-emacs@gnu.org; Mon, 16 Nov 2020 14:24:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45818) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kek6b-0006dQ-W4 for bug-gnu-emacs@gnu.org; Mon, 16 Nov 2020 14:24:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kek6b-0003NY-Sl for bug-gnu-emacs@gnu.org; Mon, 16 Nov 2020 14:24:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 16 Nov 2020 19:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44674 X-GNU-PR-Package: emacs Original-Received: via spool by 44674-submit@debbugs.gnu.org id=B44674.160555459512935 (code B ref 44674); Mon, 16 Nov 2020 19:24:01 +0000 Original-Received: (at 44674) by debbugs.gnu.org; 16 Nov 2020 19:23:15 +0000 Original-Received: from localhost ([127.0.0.1]:57364 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kek5q-0003MY-Pq for submit@debbugs.gnu.org; Mon, 16 Nov 2020 14:23:14 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:49896) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kek5p-0003MK-0L for 44674@debbugs.gnu.org; Mon, 16 Nov 2020 14:23:13 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39195) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kek5j-0006Id-LB; Mon, 16 Nov 2020 14:23:07 -0500 Original-Received: from [176.228.60.248] (port=2283 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kek5V-0008HT-QI; Mon, 16 Nov 2020 14:23:06 -0500 In-Reply-To: (message from Stefan Monnier on Mon, 16 Nov 2020 13:41:59 -0500) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:193463 Archived-At: > From: Stefan Monnier > Cc: mattiase@acm.org, p.stephani2@gmail.com, 44674@debbugs.gnu.org > Date: Mon, 16 Nov 2020 13:41:59 -0500 > > > Sorry, forgot to answer the 'system' part. The issue there is whether > > calling 'system' (and in general waiting for sub-processes to exit) is > > counted against the process's use of CPU or not. AFAIK, this is not > > well defined, either. > > Ah, I must admit that for the cases that interest me the distinction is > of no consequence. I don't even know which behavior I'd prefer. Well, we are talking about a general-purpose API, so the semantics should be well defined. And for 'clock', it isn't.