Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make the pipeline to post faster #4

Open
dannystaple opened this issue Jul 9, 2022 · 3 comments
Open

make the pipeline to post faster #4

dannystaple opened this issue Jul 9, 2022 · 3 comments
Labels

Comments

@dannystaple
Copy link
Member

Generate thoughts on making it faster:

  1. Build and push the builder image - Ie use a cache.
  2. Maybe make the builder and staging a 2 stage image.
  3. Zip up artifacts between stages might make it quicker.
  4. The repo reduction - like the clean up ticket Clean the junk and duplicates in the drafts folder. #3 might make checkouts quicker
  5. Sparse checkouts
  6. Copy more needed files at the first checkout - other checkout steps might not be needed
  7. find a smarter way to wait for things to be up than sleep 10.
  8. Bundle the two artifacts into 1 and expand.
@dannystaple
Copy link
Member Author

Generate some smaller tickets from the best of these, and see how they effect posting performance.

@dannystaple dannystaple changed the title maek the pipeline to post faster make the pipeline to post faster Jul 9, 2022
@dannystaple
Copy link
Member Author

Current timing without improvement is 7 to 8 minutes.

@dannystaple
Copy link
Member Author

Current timing is 12 minutes.
Screenshot 2023-08-20 at 12 40 51

The longest step is build site - at 7m 25s.
Where is that spending time?

  • 2m18s - building the actual site
  • 3m54s zipping up the site artifact.
    It is in that artifact so it can be used to deploy and to test. Could I speed it up by putting the actions into a single job (a bit less modular) so it doesn't need to go to and fro with that?

The staging test could be made much faster by adding a container cache - perhaps using the buildx gha cache option. That test is looking at 3 locations in the served output - verifying that htconfig is sane enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant