-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use GPU for the Container Service #51
Comments
|
Pricing per month if we use CPU vs GPU, and have ec2 instance running continually vs using EKS to launch containers:
Prices are in $USD This pricing assumes usage of 40 hours per week (8 hours a day times 5 days per week) when running directly on ec2, and 5 hours per week (1 hour per day time 5 days per week) when running via EKS. The cost of running EKS is $73.00 USD per month ($0.10 USD per hour). So running the analysis on CPU only (without EKS) is the most cost effective (assuming the usage estimates are accurate). In #44 let's see how long the analysis takes to run on the CPU |
After some test runs for #44, seems that a GPU is indeed required to run FastSurfer. See also #67 (comment) |
In #67 (comment) you said:
which command was that for? I just tried running
|
I had it from that same command |
I just ran the Then I tried running the
We could try using the |
OK so I got the same error as you now. So it seems we don't need a GPU after all? |
Created another issue for this #70 |
Since it doesn't seem essential after all, maybe we could provide it as an option? In #72 I created separate commands to run FastSurfer on a GPU or CPU, so we could let users decide which one they want to use. |
The workshop uses a container that runs some analysis with Fastsurfer. This requires a GPU to run, so we should change the ec2 instance type we're using for the Container Service
The text was updated successfully, but these errors were encountered: