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

Limit GPU usage only to where it is needed #64

Open
KTZ228 opened this issue Oct 31, 2024 · 1 comment
Open

Limit GPU usage only to where it is needed #64

KTZ228 opened this issue Oct 31, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@KTZ228
Copy link
Collaborator

KTZ228 commented Oct 31, 2024

This is more of a suggestion but given the limited number of gpu's one can use at a time, I would be curious to see whether we still need the GPU's for heating simulations.

If not, we could limit the GPU usage to acoustic simulations only so that, when acoustic simulations are done and the pipeline progresses to heating simulations, the next job can start doing acoustic simulations. That way more than 2 heating simulations can run concurrently.
But this is purely speculative. Not yet sure if this is possible.

@KTZ228 KTZ228 added the enhancement New feature or request label Oct 31, 2024
@jkosciessa
Copy link
Collaborator

This relates to #44.

I assume that heating sims also benefit from the GPU. If that is not the case, we should indeed alter the code. We can already run it like you describe it above, as the acoustic sims can be submitted with GPU. Once these are done, heating sims without GPU can be submitted.

Currently, the heating sims can require large GPU memory when specifying a pulsed repetition scheme. It would make sense to also consider optimization in that computation. (We may be creating large 4D matrices somewhere and may be able to drop the time dimension?).

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

No branches or pull requests

2 participants