From: Andreas Politz <politza@hochschule-trier.de>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Why does adding a useless copy-sequence and discarding the result make my ELisp 40 times faster?
Date: Sat, 25 Mar 2017 17:38:09 +0100 [thread overview]
Message-ID: <8737e1fh1q.fsf@luca> (raw)
In-Reply-To: 96d5bde3-fc20-750e-abc7-541b2abd2bd8@gmail.com
Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> On 2017-03-25 06:38, Andreas Politz wrote:
>> The limiting factor may also be python itself...
>>
>> ;; python2
>> ((0.114342188 0 0.0)
>> (0.715895279 0 0.0)
>> (2.120252213 0 0.0)
>> (1.02429565 0 0.0))
>>
>> ;; bash = "while read;do : ;done"
>> ((2.008305836 0 0.0)
>> (1.999825023 0 0.0)
>> (2.026715753 0 0.0)
>> (2.060320318 0 0.0))
>
> Interesting! But doesn't this just show that bash is uniformly slow?
This suggests to me, that the deciding factor in these numbers is python
and not Emacs.
Maybe it has a read buffer of a certain size, let's say 65536 ;O), and
if that buffer runs out of space, things get stalled.
-ap
next prev parent reply other threads:[~2017-03-25 16:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 4:06 Why does adding a useless copy-sequence and discarding the result make my ELisp 40 times faster? Clément Pit-Claudel
2017-03-25 4:24 ` Clément Pit-Claudel
2017-03-25 7:05 ` Eli Zaretskii
2017-03-25 10:38 ` Andreas Politz
2017-03-25 13:49 ` Clément Pit-Claudel
2017-03-25 16:38 ` Andreas Politz [this message]
2017-03-25 17:02 ` Clément Pit-Claudel
2017-03-25 17:26 ` Eli Zaretskii
2017-03-25 17:40 ` Andreas Politz
2017-03-25 17:49 ` Eli Zaretskii
2017-03-25 17:37 ` Andreas Politz
2017-03-25 13:45 ` Clément Pit-Claudel
2017-03-25 10:47 ` Andreas Politz
2017-03-25 13:54 ` Clément Pit-Claudel
2017-03-26 13:14 ` Stephen Leake
2017-03-26 13:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737e1fh1q.fsf@luca \
--to=politza@hochschule-trier.de \
--cc=cpitclaudel@gmail.com \
--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 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.