[m-dev.] Boehm parallel marking performance.

Peter Wang novalazy at gmail.com
Tue Jun 2 14:36:06 AEST 2009

2009/6/2 Paul Bone <pbone at csse.unimelb.edu.au>:
> On Tue, Jun 02, 2009 at 01:43:11PM +1000, Peter Wang wrote:
>> It would be interesting to see the improvement from parallel marking in
>> non-.par grades, and if enabling parallel marking at compile time but not
>> at runtime has any adverse effects. (Set GC_NPROCS=1)
> I thought about this breifly, intuitivly I think the synchronization required
> might make it slower, since without parallel mark in a sequential program
> synchronization is not needed at all.
> I don't understand why you would want to test parallel marking at compile time
> but then disable it at run time.

So we can compile in support for parallel marking in all C grades, knowing
that we won't incur any overhead on single core machines.  (You might also
want to deliberately disable parallel marking if the multi-core machine is
already heavily loaded.)

mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au

More information about the developers mailing list