Update bulk assign service to include iterable triggers
What does this MR do and why?
What
Update bulk assign service to include iterable triggers
- Creates iterable trigger workers for each user (min 50, max 100)
Why
Creates an iterable trigger worker for each user
DB Queries
Using 50 random user id's:
explain SELECT "users".* FROM "users" LEFT OUTER JOIN "user_details" ON "user_details"."user_id" = "users"."id" WHERE "users"."id" IN (9351, 4624, 5594, 44, 4734, 6821, 7627, 2949, 8372, 7868, 9245, 8408, 632, 1862, 2595, 6420, 6321, 6655, 6728, 9426, 5133, 6651, 9553, 1850, 6099, 8171, 9052, 2993, 3332, 4178, 4339, 8228, 6313, 7328, 8970, 6687, 5391, 9286, 63, 270, 3778, 3641, 2707, 5056, 7688, 9211, 1479, 7948, 7828, 8904)
Cold run: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/28298/commands/88326
Warm run: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/28298/commands/88327
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
No frontend changes
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to https://gitlab.com/gitlab-org/gitlab/-/issues/443471
Edited by Jay Montal