'import ccall unsafe' and parallelism

Christian Höner zu Siederdissen choener at tbi.univie.ac.at
Thu Aug 14 17:20:38 UTC 2014


I've played around some more and finally more than one capability is
active. And indeed, unsafe calls don't block everything. I /had/
actually read that but when I saw the system spending basically only
100% cpu time, I'd thought to ask.

One problem with this program seems to be that the different tasks are
of vastly different sizes. Inputs range from ~ 7x10^1 to ~ 3x10^7
elements inducing waits with the larger problem sizes.

We'll keep the program single-threaded for now as this also keeps memory
consumption at only 25 gbyte instead of the more impressive 70 gbyte in
multi-threaded mode ;-)

Viele Gruesse,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/glasgow-haskell-users/attachments/20140814/13e52465/attachment.sig>

More information about the Glasgow-haskell-users mailing list