From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r110342: Count overruns when profiling; change units to ns.
Date: Wed, 03 Oct 2012 10:29:21 -0700 [thread overview]
Message-ID: <506C75F1.3060100@cs.ucla.edu> (raw)
In-Reply-To: <83ehlfa306.fsf@gnu.org>
On 10/03/2012 10:18 AM, Eli Zaretskii wrote:
> imagine that 30% of the elapsed time that passed while profiling
> Emacs got very little or no CPU time
It's supposed to be a CPU time profiler, so that shouldn't
be a problem. Granted, hosts that don't profile CPU time
(and where we fall back on real-time) will provide inaccurate
numbers in that situation, but they're already way-inaccurate
so it doesn't really matter.
> So how about a new primitive that would return the information from
> clock_gettime (or getrusage, if clock_gettime is not available), which
> profiler.el could then use to convert timer ticks into seconds?
That should work. I would like to add an optional argument
to current-time, to specify which clock we want. But isn't
this sort of thing something that we need to delay until later?
Aren't we in a feature freeze?
next prev parent reply other threads:[~2012-10-03 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TIwjJ-0005wv-J8@vcs.savannah.gnu.org>
2012-10-02 13:20 ` [Emacs-diffs] /srv/bzr/emacs/trunk r110342: Count overruns when profiling; change units to ns Stefan Monnier
2012-10-02 16:37 ` Paul Eggert
2012-10-02 17:03 ` Eli Zaretskii
2012-10-02 20:52 ` Paul Eggert
2012-10-02 21:17 ` Eli Zaretskii
2012-10-03 5:00 ` Paul Eggert
2012-10-03 17:18 ` Eli Zaretskii
2012-10-03 17:29 ` Paul Eggert [this message]
2012-10-03 17:55 ` Eli Zaretskii
2012-10-03 2:05 ` Stefan Monnier
2012-10-03 5:03 ` Paul Eggert
2012-10-03 12:48 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506C75F1.3060100@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.