all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gemini Lasswell <gazally@runbox.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: a benchmark suite for Emacs
Date: Mon, 26 Nov 2018 17:28:26 -0800	[thread overview]
Message-ID: <87y39fgvgl.fsf@runbox.com> (raw)
In-Reply-To: <87k1kzo392.fsf@mail.linkov.net> (Juri Linkov's message of "Tue,  27 Nov 2018 01:18:17 +0200")

Juri Linkov <juri@linkov.net> writes:

>> - a local clone of a git repo
>> - a program/shell script that produces an executable given that
>>   git repo and a commit
>> - a directory in the git repo with Lisp files containing tasks to be
>>   benchmarked
>> - a range of commits (as for git-rev-list(1))
>> - a number of commits to select from the range
>>
>> it can use the shell script to build older versions of Emacs from
>> commits selected from the commit range given, run the tasks in those
>> older Emacs, record timing data, errors, process output and messages,
>> and then produce a report in the form of an org-mode file ready for
>> org-babel-gnuplot.
>
> Is it like Diffbench for Ruby?  Something like that was sorely missed
> for a long time in Emacs.

Like Diffbench, but bigger and better.  Diffbench looks like it does a
quick comparison of two states of the project.  That's something this
can do, but my vision for it is to build a database of benchmark results
for multiple machines and for commits going back as far as we can figure
out how to build and run them, so we can see how performance has changed
over time and how it varies on different systems.



      reply	other threads:[~2018-11-27  1:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  1:35 a benchmark suite for Emacs Gemini Lasswell
2018-11-26 14:16 ` Joshua Branson
2018-11-26 23:18 ` Juri Linkov
2018-11-27  1:28   ` Gemini Lasswell [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y39fgvgl.fsf@runbox.com \
    --to=gazally@runbox.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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.