the SyncMBeanImpl currently calls Session.save() for every single sync, which IMO make the synchronization methods extra expensive.
IMHO we should consider introducing a batch mode that reduces the number of save calls. the drawback of this was that the complete set of sync-calls withing a given batch would succeed or fail. in case of failure the 'original' sync-result would need to be replaced by one with operation status 'ERR'.
now that we have the basis for running benchmarks for the SyncMBeanImpl, we should be able to verify if this proposal actually has a positive impact (though benchmark results from
OAK-4119 and OAK-4120 seem to indicate that this is the case).