unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gemini Lasswell <gazally@runbox.com>
To: emacs-devel@gnu.org
Subject: a benchmark suite for Emacs
Date: Sun, 25 Nov 2018 17:35:12 -0800	[thread overview]
Message-ID: <87efb8iptb.fsf@runbox.com> (raw)

Hello all,

I've just pushed to scratch/benchmarks my WIP benchmarking suite for
Emacs and Emacs packages.

It's a long ways from done.  Some major missing parts are:

- Better/more complete user interface
- Documentation
- Statistical analysis (report on noisiness of data)
- Tramp integration/run benchmarks remotely
- Use VC rather than calling git directly
- More benchmark tasks
- Tests

But, given:

- 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.

The benchmark data is stored in a directory hierarchy organized so that
benchmark data created on separate machines can be easily git-merged
together.

There's no documentation yet, but if any of you have time and interest
in running benchmarks, let me know and I'll write up instructions.

For those of you who generously spend your time reviewing code, the new
benchmark directory, thread.el and erb-task.el are ready for your
attention, but erb.el is not.

I also welcome ideas for more benchmarks, or anyone who wants to
write some.



             reply	other threads:[~2018-11-26  1:35 UTC|newest]

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

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=87efb8iptb.fsf@runbox.com \
    --to=gazally@runbox.com \
    --cc=emacs-devel@gnu.org \
    /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).