From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Andrea Corallo <akrl@sdf.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: elisp-benchmarks
Date: Sun, 08 Dec 2019 13:05:16 -0800 [thread overview]
Message-ID: <87v9qq5y0j.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <xjf1rte5z9n.fsf@sdf.org> (Andrea Corallo's message of "Sun, 08 Dec 2019 20:38:12 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Not sure what you mean by "other package". AFAIK this is meant as
>> a benchmark of Elisp itself, so it shouldn't depend on anything
>> else than Emacs and shouldn't be affected by changes in third
>> party packages.
>
> If understand correctly that means benchmarks can probe every piece of
> Emacs core and not just 'basic' language features. To get practical: a
> test that calls the gnus infrastructure would be then acceptable right?
Right, I was also trying to imagine what this would look like in
practical terms. Say I want to put a change into Gnus that I hope will
result in speedups. I make a git branch, make some commits. I probably
set up a git worktree for the branch. I create an init file for that
worktree emacs (so that I can run "emacs -Q -l init.el") that just adds
the elisp-benchmarks package to the load-path. Then I start my worktree
emacs, and run the benchmarks.
I'm just thinking this through -- the above workflow is fine as far as
I'm concerned.
Eric
next prev parent reply other threads:[~2019-12-08 21:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 19:06 [ELPA] New package: elisp-benckmarks Andrea Corallo
2019-12-05 19:18 ` [ELPA] New package: elisp-benchmarks Andrea Corallo
2019-12-06 14:48 ` Andrea Corallo
2019-12-06 19:28 ` Eric Abrahamsen
2019-12-06 22:56 ` Andrea Corallo
2019-12-07 17:27 ` Eric Abrahamsen
2019-12-07 18:27 ` Stefan Monnier
2019-12-07 21:03 ` Eric Abrahamsen
2019-12-08 0:20 ` Stefan Monnier
2019-12-08 17:15 ` Eric Abrahamsen
2019-12-08 20:38 ` Andrea Corallo
2019-12-08 21:05 ` Eric Abrahamsen [this message]
2019-12-11 11:17 ` Andrea Corallo
2019-12-18 13:13 ` Andrea Corallo
2019-12-19 4:27 ` Stefan Monnier
2019-12-19 8:42 ` Andrea Corallo
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=87v9qq5y0j.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=akrl@sdf.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 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).