When a new field is added to a tracker, the last changeset of each tracker is retroactively updated to insert a "none" changeset value. The query that was doing the insertion in tracker_changeset_value table was looking for the last changeset id of each artifact (of the platform) before filtering out artifacts in the selected tracker. This commit leverage tracker_artifact "last_changeset_id" field that already holds the value we were recomputing at a huge cost. On our data sample with 350'000 artifacts the query went from 11s to some ms. To reviewer, please take time to carefuly review the original code to ensure I didn't mis-understand the intend of the code in first place (and, of course, that the new version does the same thing...). Part of request #22197 Creating a new field in a tracker can be slow Change-Id: Ibc1935531048d1eecb120c41255847ef5a5878d9

+12 −20

Author

Manuel Vacelet (vaceletm) 2021-07-02 17:52

Committer

Manuel Vacelet (vaceletm) 2021-07-02 17:54

Hash e82d738b7fcd69d1c8733558e843248ed5556845

Parent e09ab60c0d1dab53a0a557b412fde480c9f009ac

Reference git #tuleap/stable/e82d738b7fcd69d1c8733558e843248ed5556845