Updates use too many transactions

We notices that the transaction rate limiter gets involved a lot during Neutron operations; digging a bit further shows that Neutron uses a lot of small transactions, which could be optimised (e.g. updates could use a read-write transaction instead of a read transaction to check existence, then write transaction to update).