DataHandler has an internal check that compares the sent payload with
the state of the affected database record and removes fields from the
payload that didn't change.
Everytime a database record is updated, DataHandler resets the internal
stage to "0" to start a new editing workflow, if the affected database
table supports workspaces. This handling is unfortunately executed
*after* the payload comparison is done, leading to a payload that
always instructs to update the field `t3ver_stage`, even if the change
is not necessary, leading to superfluous database updates. This has a
massive negative performance impact in simple shared hosting
environments, especially with tt_content records that have many
file references attached.
The payload comparison is now executed after setting `t3ver_stage` to
filter out superfluous updates.