From: Ihor Radchenko <yantar92@posteo.net>
To: Emanuel Berg <incal@dataswamp.org>, Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Elisp native-comp vs. SBCL for inclist-type-hints benchmark (was: [PATCH] Re: Bignum performance)
Date: Sun, 03 Sep 2023 10:30:36 +0000 [thread overview]
Message-ID: <87fs3vmtv7.fsf@localhost> (raw)
In-Reply-To: <87wmx7mxsp.fsf@dataswamp.org>
Emanuel Berg <incal@dataswamp.org> writes:
>> Unfortunately, I cannot use this file because it is referring to
>> ~/public_html/cl/bench/timing.cl, which I do not have.
>
> It is in the same directory
>
> https://dataswamp.org/~incal/cl/bench/timing.cl
It would be nice if you attached the files to email.
Otherwise, people examining this threads a few years in future may not
be able to access the files.
> So you have to set that manually as for now.
I did, and the results are very different from yours:
$ SBCL_HOME=/usr/lib64/sbcl sbcl --load /tmp/inclist.cl
;; 1.096667 s real time
;; 1.096235 s run time
$ SBCL_HOME=/usr/lib64/sbcl sbcl --load /tmp/inclist-type-hints.cl
;; 0.55 s real time
;; 0.549992 s run time
(emacs master)
$ perf record ./src/emacs -batch -l /home/yantar92/.emacs.d/straight/repos/elisp-benchmarks/elisp-benchmarks.el --eval '(setq elb-speed 2)' --eval '(elisp-benchmarks-run "inclist")'
* Results
| test | non-gc avg (s) | gc avg (s) | gcs avg | tot avg (s) | tot avg err (s) |
|--------------------+----------------+------------+---------+-------------+-----------------|
| inclist | 1.20 | 0.00 | 0 | 1.20 | 0.02 |
| inclist-type-hints | 1.05 | 0.00 | 0 | 1.05 | 0.02 |
|--------------------+----------------+------------+---------+-------------+-----------------|
| total | 2.26 | 0.00 | 0 | 2.26 | 0.02 |
inclist: 1.1 sec vs. 1.2 sec
inclist-type-hints: 0.55 sec vs. 1.05 sec
with native-comp speed 3, the results are on par for inclist
$ perf record ./src/emacs -batch -l /home/yantar92/.emacs.d/straight/repos/elisp-benchmarks/elisp-benchmarks.el --eval '(setq elb-speed 3)' --eval '(elisp-benchmarks-run "inclist")'
* Results
| test | non-gc avg (s) | gc avg (s) | gcs avg | tot avg (s) | tot avg err (s) |
|--------------------+----------------+------------+---------+-------------+-----------------|
| inclist | 1.07 | 0.00 | 0 | 1.07 | 0.02 |
| inclist-type-hints | 0.99 | 0.00 | 0 | 0.99 | 0.00 |
|--------------------+----------------+------------+---------+-------------+-----------------|
inclist: 1.1 sec vs. 1.07 sec
inclist-type-hints: 0.55 sec vs. 0.99 sec
There is nothing obvious that is slower in Elisp - most of the time is
spent in the native compiled functions:
47.83% emacs inclist-b6453dcf-34842bf7.eln [.] F656c622d696e636c697374_elb_inclist_0
44.80% emacs inclist-type-hints-bb635d76-535ebfb0.eln [.] F656c622d696e636c6973742d7468_elb_inclist_th_0
1.45% emacs emacs [.] process_mark_stack
So, might be some missing optimization in native-comp itself.
CCing Andrea, in case if he has some insight about further analysis.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-09-03 10:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:28 [PATCH] Re: Bignum performance (was: Shrinking the C core) Gerd Möllmann
2023-08-14 6:56 ` Gerd Möllmann
2023-08-14 7:04 ` Ihor Radchenko
2023-08-14 7:35 ` Gerd Möllmann
2023-08-14 8:09 ` Ihor Radchenko
2023-08-14 9:28 ` Gerd Möllmann
2023-08-14 9:42 ` Ihor Radchenko
2023-08-15 14:03 ` Emanuel Berg
2023-08-15 15:01 ` Ihor Radchenko
2023-08-15 22:21 ` Emanuel Berg
2023-08-15 22:33 ` Emanuel Berg
2023-08-16 4:36 ` tomas
2023-08-16 5:23 ` Emanuel Berg
2023-08-14 16:51 ` Emanuel Berg
2023-08-15 4:58 ` Gerd Möllmann
2023-08-15 14:20 ` Emanuel Berg
2023-08-15 6:26 ` [PATCH] Re: Bignum performance Po Lu
2023-08-15 14:33 ` Emanuel Berg
2023-08-15 17:07 ` tomas
2023-08-15 22:46 ` Emanuel Berg
2023-08-16 1:31 ` Po Lu
2023-08-16 1:37 ` Emanuel Berg
2023-08-16 3:17 ` Po Lu
2023-08-16 4:44 ` tomas
2023-08-16 5:18 ` Gerd Möllmann
2023-08-16 5:35 ` Emanuel Berg
2023-08-18 7:14 ` Simon Leinen
2023-08-19 13:10 ` Emanuel Berg
2023-08-20 5:07 ` Ihor Radchenko
2023-08-20 6:20 ` Emanuel Berg
2023-08-28 5:32 ` Emanuel Berg
2023-09-03 0:48 ` Emanuel Berg
2023-09-03 8:50 ` Ihor Radchenko
2023-09-03 9:05 ` Emanuel Berg
2023-09-03 10:30 ` Ihor Radchenko [this message]
2023-09-04 1:03 ` Elisp native-comp vs. SBCL for inclist-type-hints benchmark (was: [PATCH] Re: Bignum performance) Emanuel Berg
2023-09-03 1:57 ` [PATCH] Re: Bignum performance Emanuel Berg
2023-09-04 4:13 ` Emanuel Berg
2023-08-16 5:41 ` Gerd Möllmann
2023-08-16 6:42 ` Po Lu
2023-08-16 8:05 ` Gerd Möllmann
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=87fs3vmtv7.fsf@localhost \
--to=yantar92@posteo.net \
--cc=acorallo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=incal@dataswamp.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).