From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-devel@gnu.org
Cc: Mark H Weaver <mhw@netris.org>
Subject: Re: Unexpectedly low read/write performance of open-pipe
Date: Mon, 22 Apr 2019 20:39:03 +0200 [thread overview]
Message-ID: <87ftq9khq0.fsf@web.de> (raw)
In-Reply-To: <87zhojjplg.fsf@trouble.defaultvalue.org>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Rob Browning <rlb@defaultvalue.org> writes:
>> For something similar to the original python code and roughly similar to
>> open-pipe OPEN_BOTH (see code below) I see:
>> mb/s: 1713.26754296
> Here for "guile -s io-perf.scm > /dev/null" I see:
>
> 2.2.4: 1.39 mb/s >100% CPU in top
> your first proposal: 1453.49 mb/s >300% CPU in top
> this series: 3937.01 mb/s <80% CPU in top
Is this still on the same machine? If yes, then it would show a more
than 2x speedup cmpared to Python!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2019-04-22 18:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 18:28 Unexpectedly low read/write performance of open-pipe Rob Browning
2019-04-07 18:45 ` Rob Browning
2019-04-07 19:47 ` Rob Browning
2019-04-07 21:28 ` Rob Browning
2019-04-08 10:52 ` Mark H Weaver
2019-04-09 6:56 ` Rob Browning
2019-04-09 8:35 ` Mark H Weaver
2019-04-09 9:21 ` Chris Vine
2019-04-09 18:24 ` Mark H Weaver
2019-04-09 21:36 ` Chris Vine
2019-04-10 0:07 ` Mark H Weaver
2019-04-16 21:42 ` Mark H Weaver
2019-04-09 18:33 ` Mark H Weaver
2019-04-17 4:02 ` Mark H Weaver
2019-04-21 16:22 ` Rob Browning
2019-04-22 18:39 ` Arne Babenhauserheide [this message]
2019-04-23 7:32 ` tomas
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftq9khq0.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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.
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).