unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Siraphob (Ben) Phipathananunth" <siraben@disroot.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: johnw@gnu.org, emacs-devel@gnu.org
Subject: An Emacs benchmarking suite (was: An idea, now that we have dynamic loading)
Date: Fri, 11 May 2018 22:22:47 +0700	[thread overview]
Message-ID: <0af8a67e-3403-8e81-a666-78b3d8da54b1@disroot.org> (raw)
In-Reply-To: <83bmdmnskd.fsf@gnu.org>

Eli Zaretskii wrote:
> John even asked for creation of such a suite of performance tests, but
> AFAIK no one has picked the gauntlet till now.

Would it suffice to use Emacs Lisp to run these performance tests
(i.e. using benchmark.el)?  Even so, how would one account for
external factors in the operating system?  Perhaps when the test is
performed, the deltas between commits are given as percentages instead
of CPU time.  Once we have that, it would be great to have tests run
multiple times and/or on various devices to refine the data further.

An area that would be interesting to look at is memory usage of
functions over commits, but I don't know of a way of measuring memory
usage in Emacs (especially over an extended period, to analyze things
such as maximum memory usage).

-- 
Siraphob (Ben) Phipathananunth



  reply	other threads:[~2018-05-11 15:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06  1:44 An idea, now that we have dynamic loading John Wiegley
2018-05-06  2:25 ` Óscar Fuentes
2018-05-10 12:45 ` Siraphob (Ben) Phipathananunth
2018-05-10 20:31   ` John Wiegley
2018-05-11  6:11     ` Eli Zaretskii
2018-05-11  7:56       ` John Wiegley
2018-05-11 14:59       ` Siraphob (Ben) Phipathananunth
2018-05-11 15:02         ` Eli Zaretskii
2018-05-11 15:22           ` Siraphob (Ben) Phipathananunth [this message]
2018-05-11 17:38             ` An Emacs benchmarking suite (was: An idea, now that we have dynamic loading) Eli Zaretskii
2018-05-14 11:37               ` An Emacs benchmarking suite Phillip Lord
2018-05-14 16:18                 ` Eli Zaretskii
2018-05-14 16:30                   ` Stefan Monnier
2018-05-15 13:24                     ` Phillip Lord
2018-05-10 13:58 ` An idea, now that we have dynamic loading Tom Tromey
2018-05-10 20:31   ` John Wiegley
2018-05-14 21:44     ` Tom Tromey
2018-05-14 23:36       ` John Wiegley
2018-05-21 21:13         ` Tom Tromey
2018-05-22  3:23           ` John Wiegley
2018-05-22  4:20             ` Tom Tromey

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=0af8a67e-3403-8e81-a666-78b3d8da54b1@disroot.org \
    --to=siraben@disroot.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@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).