BUG-650: improve modification sealing performance 26/11126/2
authorRobert Varga <rovarga@cisco.com>
Fri, 12 Sep 2014 21:47:17 +0000 (23:47 +0200)
committerRobert Varga <rovarga@cisco.com>
Sat, 13 Sep 2014 13:41:39 +0000 (15:41 +0200)
commit2ff3d8442e0996681953cf73f5172f90c2507b4a
tree06cd6addace79203a5cb2770248afa1f69b1433c
parentf8ad031084ce2bfd11bec9aeed9d94437863f696
BUG-650: improve modification sealing performance

The seal operation is on a fast path, so performing synchronization is
not really advised. Downgrade synchronized blocks to volatile
modifications, which have better effects on the optimizer. We introduce
a SynchronizedDataTreeModification which the users can use when they
require a serialized thread-safe access.

Change-Id: Ieffcf1f5fef4d4df32fcdc30f992672d79dcf7bf
Signed-off-by: Robert Varga <rovarga@cisco.com>
yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/tree/SynchronizedDataTreeModification.java [new file with mode: 0644]
yang/yang-data-impl/src/main/java/org/opendaylight/yangtools/yang/data/impl/schema/tree/InMemoryDataTreeModification.java