[Mono-list] Large object heap size threshold

[Matt Calder]

Rodrigo,

Thanks for the quick response. Following your suggestion, in sgen-conf.h I
see:

/*
 * Objects bigger then this go into the large object space.  This size
 * has a few constraints.  It must fit into the major heap, which in
 * the case of the copying collector means that it must fit into a
 * pinned chunk.  It must also play well with the GC descriptors, some
 * of which (DESC_TYPE_RUN_LENGTH, DESC_TYPE_SMALL_BITMAP) encode the
 * object size.
 */
#define SGEN_MAX_SMALL_OBJ_SIZE 8000

I am wondering what is the size of a pinned chunk? Also what does "play
well" entail? Perhaps more to the point, if I set that number to say:

#define SGEN_MAX_SMALL_OBJ_SIZE 64000

do I run afoul of any constraints? Thanks for answering this,

Matt




On Tue, Jan 14, 2014 at 8:12 PM, Rodrigo Kumpera <kumpera at gmail.com> wrote:

> For sgen it's 8000 and it's configurable at the source level. See
> sgen-conf.h
>
>
> On Tue, Jan 14, 2014 at 5:11 PM, Matt Calder <mvcalder at gmail.com> wrote:
>
>> It is my understanding that the large object heap is where allocations
>> are made for objects larger than 4K. Is that correct and is it possible to
>> configure that threshold to be larger? Thanks,
>>
>> Matt
>>
>> _______________________________________________
>> Mono-list maillist  -  Mono-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20140115/cabe143d/attachment.html>