From: Rob Browning <rlb@defaultvalue.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Unexpectedly low read/write performance of open-pipe
Date: Sun, 21 Apr 2019 11:22:03 -0500 [thread overview]
Message-ID: <87zhojjplg.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87zhop46u4.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> I've attached four patches. Only the first two should be needed for
> what I have described above.
>
> The last two patches will only be of interest if you need suspendable
> I/O. They add suspendable I/O support for custom binary ports, and in
> particular for these OPEN_BOTH pipe ports.
>
> Note that I've not yet done much testing of these patches, besides
> running the Guile test suite.
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
(and most importantly for this series, a much quieter fan...)
And yes, I'd love to see something like this in 2.2 too if it turns out
to be feasible to include it there.
Nice
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2019-04-21 16:22 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 [this message]
2019-04-22 18:39 ` Arne Babenhauserheide
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=87zhojjplg.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).