[Gc] Re: Are there any tuning options for thread local allocator?
pbone at csse.unimelb.edu.au
Sun Oct 31 15:15:14 PST 2010
On Tue, Oct 05, 2010 at 04:01:51AM +0000, Boehm, Hans wrote:
> The allocation is still the bottleneck? What sizes of objects are being allocated?
> It should normally be allocating on the order of HBLKSIZE bytes per lock acquisition. But it only does so for objects up to about 256 bytes. And only after the allocating thread has warmed up and allocated a bunch of objects of that size.
> It may work to increase HBLKSIZE. That probably has a better chance of working if MPROTECT_VDB does not get defined.
> If the problem is really in the marker, you may want to make sure that PARALLEL_MARK is also turned on.
This helped sagnificantly in one particular GC heavy program, as did increating
the initial heapsize to reduce the number of times the world was stopped.
We want to do more testing before we report on this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 490 bytes
Desc: Digital signature
Url : https://napali.hpl.hp.com/pipermail/gc/attachments/20101101/462fdc13/attachment.pgp
More information about the Gc