GNU bug report logs - #22114
24.5; [PATCH] Allow profiler.el to display reports after stopping

Previous Next

Full log

View this message in rfc822 format

From: John Wiegley <jwiegley <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22114 <at> debbugs.gnu.org, Vasilij Schneidermann <v.schneidermann <at> gmail.com>
Subject: bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping
Date: Tue, 08 Dec 2015 09:42:37 -0800

[Message part 1 (text/plain, inline)]

>>>>> Eli Zaretskii <eliz <at> gnu.org> writes:

> But why would you need a subsequent access to the same data? The profiler
> report is in the buffer, and you can review it whenever you want. The buffer
> has the time of the report creation as part of its name, so the next report
> will not destroy the buffer. You can also save the report to a file (there's
> a separate command to do that). By contrast,producing a report again from
> the same data will simply produce an identical report.

> I guess I don't see a use case where the user would need to produce the same
> report twice. I never needed that myself, FWIW.

I think the OP wants to:

  1. Start a profile
  2. View the "results in progress"
  3. Allow it to continue execution
  4. View the "results at the end"

It's step #2 that's missing. If we can only view the results in progress by
taking away the option for #4, this is less optimal.

This is something that other profilers do let you do; I use Instruments on the
Mac to view "statistics as they happen" all the time, to spot trends, for
example.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.