From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org, 14518@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: C and Emacs Lisp code parts
Date: Wed, 6 Jul 2016 09:25:54 +0200 [thread overview]
Message-ID: <fc7419b6-3544-3204-357f-2739a83669d5@online.de> (raw)
In-Reply-To: <m2a8hvzood.fsf@newartisans.com>
On 06.07.2016 00:48, John Wiegley wrote:
>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> In which you were asked to provide some numbers, but gave none. Please do
>> provide them, and perhaps that bug could be taken care of.
> Until we have numbers, no action will be taken here. I am still of the
> position that *more* code should be moved from C to Emacs Lisp, and not the
> other way around.
>
> If there are cases where this might be a bad idea, measurement is needed to
> convince me. As others have said, performance is a complex beast, and human
> guesses about how a modern machine operates are more often wrong than not.
>
M-x elp-instrument-function RET define-abbrevs RET
do some edits
M-x elp-results RET
abbrev--describe 36050 15.224345396 0.0004223119
abbrev-edit-save-buffer 1 8.034011581 8.034011581
abbrev-edit-save-to-file 1 8.033998314 8.033998314
abbrev--write 18025 5.8414600190 0.0003240754
define-abbrevs 1 1.334075568 1.334075568
abbrev-get 107835 0.5151135200 4.776...e-06
abbrev-table-get 36964 0.1173239610 3.174...e-06
abbrev-table-put 18320 0.0690998279 3.771...e-06
abbrev-table-empty-p 584 0.010703864 1.832...e-05
abbrev-table-p 584 0.0050513859 8.649...e-06
abbreviate-file-name 91 0.002899625 3.186...e-05
abbrev-table-name 2 0.000254252 0.000127126
abbrev-mode 1 1.4463e-05 1.4463e-05
next prev parent reply other threads:[~2016-07-06 7:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 8:03 C and Emacs Lisp code parts Andreas Röhler
2016-07-01 8:13 ` Eli Zaretskii
2016-07-01 8:39 ` Andreas Röhler
2016-07-01 9:16 ` Alan Mackenzie
2016-07-01 12:07 ` Andreas Röhler
2016-07-01 13:04 ` Eli Zaretskii
2016-07-05 22:48 ` John Wiegley
2016-07-06 7:25 ` Andreas Röhler [this message]
2016-07-06 7:31 ` Andreas Röhler
2016-07-06 15:27 ` Phillip Lord
2016-07-01 9:17 ` John Wiegley
2016-07-01 13:26 ` Andreas Röhler
2016-07-01 9:25 ` Eli Zaretskii
2016-07-01 12:25 ` Andreas Röhler
2016-07-01 13:01 ` Eli Zaretskii
2016-07-01 13:05 ` Andy Moreton
2016-07-01 15:14 ` Karl Fogel
2016-07-01 16:52 ` Andreas Röhler
2016-07-01 17:13 ` Eli Zaretskii
2016-07-01 17:36 ` Andreas Röhler
2016-07-01 17:38 ` Eli Zaretskii
2016-07-02 16:41 ` Fabrice Popineau
2016-07-02 17:16 ` Eli Zaretskii
2016-07-01 17:55 ` Alan Mackenzie
2016-07-01 18:31 ` Andreas Röhler
2016-07-01 18:57 ` Alan Mackenzie
2016-07-01 20:04 ` Andreas Röhler
2016-07-01 20:31 ` Davis Herring
2016-07-02 6:34 ` Andreas Röhler
2016-07-02 11:29 ` Paul Eggert
2016-07-05 17:02 ` Davis Herring
2016-07-05 19:35 ` Andreas Röhler
2016-07-02 6:32 ` Eli Zaretskii
2016-07-02 7:01 ` Andreas Röhler
2016-07-02 8:15 ` Eli Zaretskii
2016-07-02 3:32 ` Tom Tromey
2016-07-02 3:42 ` Clément Pit--Claudel
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=fc7419b6-3544-3204-357f-2739a83669d5@online.de \
--to=andreas.roehler@online.de \
--cc=14518@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).