This is an internal enhancement to the update bean processing.
Specifically adding in a cachable "Update Plan" ... that can be reused. This covers all scenarios (update all properties, update only changed properties) except for the concurrency mode = all.
With concurrency mode = all... the where clause is very dynamic due to the required use of "is null" in the SQL and so at this stage we are not bothering to cache that update plan.
Otherwise, the performance can be expected to improve - due to the skipping of some processing - especially when in 'update only changed properties' mode.