after upgrading from 3.1 to 4.5 I notice an increased load on our repository, which is mostly due to “require(‘ui/onUpdateUser’).preserveLastSync(object, oldObject, request);” in managed_onUpdate.
In the past it took one insert operation to managedobjects to create a new user, now it is one insert and 15 updates, due to 15 mappings, each updating preserveLastSync. And this results in an increase of audit-entries as well, since each updated lastSync-timestamp results in an audit-entry.
Is there anything to be aware of? I’d like to disable it, but I’m not sure how or if lastSync is used at all.