From: ludo@gnu.org (Ludovic Courtès)
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>,
13188-done@debbugs.gnu.org, guile-devel@gnu.org
Subject: Re: Whats' the proper senario of par-map? (Was Re: bug#13188: par-map causes VM stack overflow)
Date: Fri, 29 Mar 2013 10:52:51 +0100 [thread overview]
Message-ID: <87ppyimt1o.fsf@gnu.org> (raw)
In-Reply-To: <1364524610.2730.48.camel@Renee-desktop.suse> (Nala Ginrut's message of "Fri, 29 Mar 2013 10:36:50 +0800")
Nala Ginrut <nalaginrut@gmail.com> skribis:
> And there're two possible applications:
> 1. handle the requests in a server
> 2. read files from disk (but how big file is proper for par-map)
Quoting the fine manual:
Note that futures are intended for the evaluation of purely
functional expressions. Expressions that have side-effects or rely on
I/O may require additional care, such as explicit synchronization (*note
Mutexes and Condition Variables::).
IOW, think twice before you use it for something not purely computational.
:-)
Ludo’.
prev parent reply other threads:[~2013-03-29 9:52 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
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 [this message]
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=87ppyimt1o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=13188-done@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=nalaginrut@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).