From: David Pirotte <david@altosw.be>
To: 14756@debbugs.gnu.org
Subject: bug#14756: threads - par-map - multicore issue
Date: Sun, 30 Jun 2013 15:00:54 -0300 [thread overview]
Message-ID: <20130630150054.07f19f35@capac> (raw)
Hello,
guile --version
guile (GNU Guile) 2.0.9.20-10454
It seems that the par-map not using all cores problem has some how been reintroduced?
guile -c '(begin (use-modules (ice-9 threads)) (par-map 1+ (iota 400000)))'
only uses 1 core [it seems it uses some other [maybe all, i can't tell] a couple of
milliseconds, then drops to 1 core only.
Thanks,
David
;; --
david@idefix:~ 16 $ guile -c '(begin
> (use-modules (ice-9 threads))
> (par-map 1+ (iota 400))
> (display (current-processor-count)) (display "\n")
> (display (length (@@ (ice-9 futures) %workers))) (display "\n"))'
12
11
next reply other threads:[~2013-06-30 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 18:00 David Pirotte [this message]
2016-06-21 6:51 ` bug#14756: threads - par-map - multicore issue Andy Wingo
2016-06-21 8:33 ` Ludovic Courtès
2017-02-28 9:53 ` Andy Wingo
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=20130630150054.07f19f35@capac \
--to=david@altosw.be \
--cc=14756@debbugs.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.
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).