https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1920 controller <p>When CDS is faced with large transactions it can easily allocate byte[]s whose size is couple of megabytes. This is problematic with G1GC, as such objects are allocated as humongous objects in the old generation – if they exceed one-half of region size. Region size varies between 1MiB and 32MiB and is recommended to be sized at 1/2048 of heap.</p> <p>The source of these is CommitTransactionPayload, which retains its serialized form – which is used to write it out either to persistence or to followers. We should be able to store this serialized form in a format which does not rely on such large objects.</p> <p> </p> CONTROLLER-1920

CommitTransactionPayload results in humongous objects being allocated

Bug Medium Resolved Done Robert Varga Robert Varga Mon, 23 Sep 2019 12:46:30 +0000 Thu, 10 Oct 2019 09:06:41 +0000 Thu, 10 Oct 2019 09:06:41 +0000 Nitrogen SR3 Oxygen SR4 Sodium Fluorine SR3 Neon SR2 Magnesium Sodium SR1 Neon SR3 clustering 0 2 <p><a href="https://www.oracle.com/technetwork/articles/java/g1gc-1984535.html" class="external-link" target="_blank" rel="nofollow noopener">https://www.oracle.com/technetwork/articles/java/g1gc-1984535.html</a> details the handling of humongous objects and notes that the region size should be increased to eliminate such objects if they end up causing old gen fragmentation and back-to-back concurrent cycles. Given the overall overhead, it seems it is a much better strategy to just cap the size of the arrays we allocate here.</p> Development Rank 0|i03p4n: