Trigger a GC once initial configuration has been pushed 03/7003/1
authorRobert Varga <rovarga@cisco.com>
Wed, 14 May 2014 22:04:17 +0000 (00:04 +0200)
committerRobert Varga <rovarga@cisco.com>
Wed, 14 May 2014 22:04:17 +0000 (00:04 +0200)
commitc0b10c35abcdf8038546aa89bf29264720f12a75
treecd5d43a42268e1545357cf35abdda8a4072fd5b3
parentb2d51144854503513151435f164510ef0dd47b1f
Trigger a GC once initial configuration has been pushed

This introduces a single run of GC once we complete the initial
configuration.

The reasoning behind that is that we generate a fair amount of metadata
which we are likely to retain unmodified for extended periods of time.
We take care to store it in both memory and CPU efficient format, which
unfortunately requires us to do some copying around to compact it,
leaving a sizeable chunk of garbage on the heap.

Change-Id: I81af7d317e3b6f82a431e78b5fb439d8cb5f1997
Signed-off-by: Robert Varga <rovarga@cisco.com>
opendaylight/netconf/config-persister-impl/src/main/java/org/opendaylight/controller/netconf/persist/impl/osgi/ConfigPersisterActivator.java