ci: Move Synapse start to beginning of workflow - #5855
Closed
backspace wants to merge 1 commit into
Closed
Conversation
Synapse takes about 67s to answer its healthcheck, and `create realm users` does nothing but wait for it: in a shard log, all twelve realm users queue at 18:34:33 and the first registration request goes out at 18:35:03, a 30s gap that is entirely Synapse coming up. Starting it just before the index import (measured on #5854) hid only the ~24s the import takes, so the gate still waited 38s and setup did not move. Start it as early as the image allows instead — right after Traefik, before the asset download, skills-realm population, the remaining image warm and the import — so roughly the whole boot happens behind work the shard has to do anyway. The warm action grows an `images` input so this can pull just the Synapse image and leave the other four to the existing step; `all` remains the default for every other caller. Expected: `create realm users` falls toward the ~2s the registrations themselves take, without `Wait for realms` growing to absorb it. If the wait does grow, realm-server's own boot is the next wall rather than Synapse's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Contributor
Author
|
it didn’t help! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an iteration of #5854, stacked on #5850. Synapse takes long enough that starting in first might help.
Claude explanation
Synapse takes about 67s to answer its healthcheck, and `create realm users` does nothing but wait for it: in a shard log, all twelve realm users queue at 18:34:33 and the first registration request goes out at 18:35:03, a 30s gap that is entirely Synapse coming up.Starting it just before the index import (measured on #5854) hid only the ~24s the import takes, so the gate still waited 38s and setup did not move. Start it as early as the image allows instead — right after Traefik, before the asset download, skills-realm population, the remaining image warm and the import — so roughly the whole boot happens behind work the shard has to do anyway.
The warm action grows an
imagesinput so this can pull just the Synapse image and leave the other four to the existing step;allremains the default for every other caller.Expected:
create realm usersfalls toward the ~2s the registrations themselves take, withoutWait for realmsgrowing to absorb it. If the wait does grow, realm-server's own boot is the next wall rather than Synapse's.