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

Scalability and performance #122

Open
manthey opened this issue Mar 26, 2024 · 1 comment
Open

Scalability and performance #122

manthey opened this issue Mar 26, 2024 · 1 comment

Comments

@manthey
Copy link
Contributor

manthey commented Mar 26, 2024

We'd like to conduct an experiment to determine the effect of different CPU/GPU and memory on performance.

A proposed course of work (feedback encouraged):

We could deploy an instance of DSA on different AWS EC2 instances and compare the time for first superpixel and feature generation and the time of a few training iterations.

Possible things to compare to produce some benchmarks:

  • number of cpus or cores
  • availability of gpu (possibly try different gpu classes)
  • memory (often coupled with cpus)
  • images on local block storage versus S3
  • number of images. We could have a few test sets, maybe take a large number of images from the TCGA collection and measure the speed of different numbers of images in the different configurations. Ideally, we'd like to try sets that substantially exceed the number of cpu cores so the work can saturate the hardware. I might try powers of 2 or 4 (e.g, 1 image, 4, 16, 64, ...)

Ideally we'd have some infrastructure-as-code way to deploy this so that we can reproduce the results, at least for deploying to a specific EC2 instance style and uploading our data, even if we kick off the individual jobs manually.

@manthey
Copy link
Contributor Author

manthey commented Mar 26, 2024

@bnmajor @jeffbaumes I'd love for one outcome of this to be some description of how to deploy DSA with a custom provisioning file to EC2 in some standardized manner (recognizing that the girder-next work may change what we do).

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

No branches or pull requests

1 participant