Skip to content
New issue

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

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

Already on GitHub? # to your account

Discussion: Performance improvements #150

Closed
craig-willis opened this issue Jun 7, 2021 · 1 comment
Closed

Discussion: Performance improvements #150

craig-willis opened this issue Jun 7, 2021 · 1 comment

Comments

@craig-willis
Copy link
Collaborator

(Replaces #140)

Problems:

  • Building and pushing images can take a long time
  • Spawning instances can take a long time when images need to be pulled to the nodes

Ideas:

  • Try to build image on the same node it was last built on
  • Run the instance on the same node it was last built on
  • Make push async on launch -- no need to wait for push to run
  • Make sure nightly cache rebuilds are also pushed to registry has up-to-date copy of base images

Many of these hinge on storing the last-known-node-id and submitting to the queue directly, which has apparent problems for distributing workloads. (Can we "suggest" a node to celery?)

@craig-willis
Copy link
Collaborator Author

Largely solved by new caching strategy.

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

No branches or pull requests

1 participant