Hello, Tom, Robert, Stephen, Does commiting a transaction with no put/.../merge/delete operations on that Tx have any noteworthy (real life) overhead compared to cancelling it?
I am asking because that has come up in https://git.opendaylight.org/gerrit/#/c/74506/1/lockmanager/lockmanager-impl/src/main/java/org/opendaylight/genius/lockmanager/impl/LockManagerServiceImpl.java@a229 and I was wondering if there is any point in making our ManagedNewTransactionRunner "smarter" so that it does a cancel if it wasn't actually used. My initial reaction is that such an optimization in ManagedNewTransactionRunner is probably pointless as whatever happens behind the scenes on a commit is surely already smart enough by itself for a submit on an empty transaction to basically be a low overhead NOOP anyway? Tx, M. -- Michael Vorburger, Red Hat vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
