On 1/10/20 6:00 PM, guile-user-requ...@gnu.org wrote:
> Message: 1
> Date: Fri, 10 Jan 2020 16:08:25 +
> From: Chris Vine
> To: Zelphir Kaltstahl
> Cc: Guile User
> Subject: Re: Limiting parallelism using futures, parallel forms and
> fibers
> Mes
On Fri, 10 Jan 2020 01:43:18 +0100
Zelphir Kaltstahl wrote:
> Hi Chris!
>
> On 1/8/20 12:44 PM, Chris Vine wrote:
> > On Wed, 8 Jan 2020 08:56:11 +0100
> > Zelphir Kaltstahl wrote:
> > [snip]
> >> So my questions are:
> >>
> >> - Is there a default / recommended way to limit parallelism for
>
Hi Chris!
On 1/8/20 12:44 PM, Chris Vine wrote:
> On Wed, 8 Jan 2020 08:56:11 +0100
> Zelphir Kaltstahl wrote:
> [snip]
>> So my questions are:
>>
>> - Is there a default / recommended way to limit parallelism for
>> recursive calls to parallel forms?
>>
>> - Is there a better way than a global
Thanks for your suggestion, I will take it into account.
Regards,
Zelphir
On 1/8/20 9:11 AM, Linus Björnstam wrote:
> Hi!
>
> I don't have much more input than to say that futures use a built in thread
> pool that is limited to (current-processor-count) threads. That could maybe
> be
On Wed, 8 Jan 2020 08:56:11 +0100
Zelphir Kaltstahl wrote:
[snip]
> So my questions are:
>
> - Is there a default / recommended way to limit parallelism for
> recursive calls to parallel forms?
>
> - Is there a better way than a global counter with locking, to limit the
> number of futures
Hi!
I don't have much more input than to say that futures use a built in thread
pool that is limited to (current-processor-count) threads. That could maybe be
modified using setaffinity ?
Hope this helps.
--
Linus Björnstam
On Wed, 8 Jan 2020, at 08:56, Zelphir Kaltstahl wrote:
> Hello
Hello Guile users!
I thought about what I need for parallelizing an algorithm I am working
on. Background: I am working on my decision tree implementation
(https://notabug.org/ZelphirKaltstahl/guile-ml/src/wip-port-to-guile),
which is currently only using a single core. Training the model splits
