From: Mark H Weaver <mhw@netris.org>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Extremely high overhead of 'par-map'
Date: Fri, 29 Mar 2013 19:18:04 -0400 [thread overview]
Message-ID: <87li9594nn.fsf@tines.lan> (raw)
In-Reply-To: <CA+U71=P5TEEGGVXg3Q0dmV_J0nbDXZ8f00G3BAJdQAHJSGqW-w@mail.gmail.com> (Noah Lavine's message of "Fri, 29 Mar 2013 16:27:17 -0400")
Hi Noah,
Noah Lavine <noah.b.lavine@gmail.com> writes:
> Oh, sorry to email twice so soon, but I have an idea for making
> par-map usable in more cases: add a keyword argument called
> "block-size". Its value should be a positive integer, and the meaning
> is to have each thread do block-size iterations.
IMO, we should avoid adding anything like this. It would be hard for
callers to know what value to pass. I think it should be possible to
make 'par-map' act sensibly and efficiently without this kind of help.
> I tried to benchmark it, but got a segmentation fault. I think we
> have plenty of work to do here. :-)
Ouch. Can you please file a bug report with the full details?
Regards,
Mark
next prev parent reply other threads:[~2013-03-29 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1355559152.27310.5.camel@Renee-desktop.suse>
[not found] ` <87y5d8rclr.fsf@gnu.org>
2013-03-28 2:55 ` Whats' the proper senario of par-map? (Was Re: bug#13188: par-map causes VM stack overflow) Nala Ginrut
2013-03-28 5:05 ` Mark H Weaver
2013-03-28 13:44 ` Ludovic Courtès
2013-03-28 18:00 ` Mark H Weaver
2013-03-28 20:07 ` Ludovic Courtès
2013-03-29 2:36 ` Nala Ginrut
2013-03-29 5:49 ` Mark H Weaver
2013-03-29 6:00 ` Extremely high overhead of 'par-map' Mark H Weaver
2013-03-29 20:24 ` Noah Lavine
2013-03-29 20:27 ` Noah Lavine
2013-03-29 23:18 ` Mark H Weaver [this message]
2013-03-30 23:37 ` Ludovic Courtès
2013-03-29 16:45 ` Whats' the proper senario of par-map? (Was Re: bug#13188: par-map causes VM stack overflow) Mark H Weaver
2013-04-01 19:10 ` Andy Wingo
2013-03-29 9:52 ` Ludovic Courtès
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=87li9594nn.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).