high CPU on ODL startup

When starting ODL it seems to consume all available CPU - for anywhere upwards of 20 CPU minutes (I'm testing on a quad CPU system). If I increase controller logging to debug then the CPU seems to get soaked indefinitely (I gave up after about 90 minutes of CPU time - ODL still hadn't finished startup).

Once ODL finishes startup (NETCONF is up to my 4 routers and BGP-LS is up to the one BGP-LS speaker) then CPU returns to a normal level.

I'm wondering if this issue was introduced by the change from configuration over netconf to direct use of Java APIs (I'm pretty sure I didn't see it before that change).

logs for the case with controller logging set to INFO showed that it took just over 5 minutes to get to the end of the configuration persister.

attached (and zipped) logs for the case where controller logging was set to DEBUG show that after 9 or 10 minutes we run out of heap space and there were no more logs. MAVEN_OPTS was set to "-Xmx1024m -XX:MaxPermSize=512m".