From: John Wiegley <jwiegley@gmail.com>
To: Dhavan Vaidya <quark@codingquark.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs benchmarking suite
Date: Sat, 19 Mar 2016 16:32:58 -0700 [thread overview]
Message-ID: <m2egb6vyad.fsf@newartisans.com> (raw)
In-Reply-To: <1458384791.7944.32.camel@codingquark.com> (Dhavan Vaidya's message of "Sat, 19 Mar 2016 16:23:11 +0530")
>>>>> Dhavan Vaidya <quark@codingquark.com> writes:
> On the topic, Sacha interviewed Johnw recently in which he mentioned the
> need of having a benchmarking/profiling system for emacs. He says the
> performance has been decreasing over time.
Hi Dhavan!
I should clarify: John has the perception that it has been decreasing, but
this may not at all be the case. Hence the need for measurement. :)
> Share your thoughts on this, give me guidelines and help would be much
> appreciated!
Investing some time in learning a bit of Lisp is a good idea; even better will
be to find a buddy/collaborator who can help you to architect a benchmarking
framework, ideally based on work that has already been done for this sort of
thing in other language.
We want to be able to measure resource usage of Lisp code, to compare this
usage against previous runs (say, build to build), and a way of charting the
progression over time. This way, a dev who builds Emacs frequently can watch
for trends over time.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
prev parent reply other threads:[~2016-03-19 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 10:53 Emacs benchmarking suite Dhavan Vaidya
2016-03-19 11:57 ` Marcin Borkowski
2016-03-19 12:15 ` Dhavan Vaidya
2016-03-19 16:13 ` Drew Adams
2016-03-19 23:32 ` John Wiegley [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2egb6vyad.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=quark@codingquark.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).