performance problem for Org Identity Source ‘Source record is unchanged, no changes were processed’

Michael Gettes Today at 17:12

(on 4.0.2) Is it really necessary to log in cm_co_job_history_records an entry with comment ‘Source record is unchanged, no changes were processed’?  I’d like to think we’d get a bit of a speed up without this possibly unnecessary logging.  Some rough math: with 70K records and let’s declare all are not changing - and about 50ms for a DB update - that saves about 1 hour processing time.  and 50ms might be too quick so savings might be longer.

Michael Gettes  3 hours ago

also - i am NOT asking for a change to 4.0.2 - changes in 4.1 - if appropriate - are fine.
----New
Benn Oshrin  3 minutes ago

IIRC that message was intended to address the “wait, why didn’t that record get processed?” sort of query, but it is noisy for larger installations, and maybe should be configurable one way or the other. Feel free to open a JIRA for it, even better if you have a test instance and can comment out the creation of that entry to see what the actual speed up is.