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.

Sign up for GitHub

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

Jump to bottom

Switching devices to CPU for MaxPooling2DLayer #233

Closed
m-usama-z opened this issue Aug 5, 2024 · 2 comments
Closed

Switching devices to CPU for MaxPooling2DLayer #233

m-usama-z opened this issue Aug 5, 2024 · 2 comments

Comments

@m-usama-z
Copy link

Hi. For performance reasons, it seems useful to switch devices to CPU for MaxPooling2DLayer, and then switch back to GPU if the original device were GPU. Although, I only observed performance on a few examples so I cannot yet speak for the general case.
@mldiego
Copy link
Collaborator

mldiego commented Aug 20, 2024

Thanks for catching this! However, it may depend on the hardware (CPU, GPU) and OS used, so we'll keep this in mind, but an analysis over different OS and hardware may be needed. For now, we'll keep it customizable for users to choose the computation device.

@mldiego mldiego closed this as completed Aug 20, 2024
@m-usama-z
Copy link
Author

Thank you for that information. Instead of the option to use GPU throughout the reachability analysis, it may be more useful to make it an option to use GPU only for convolutional layer (or only for any such layers where it's known to actually improve performance).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mldiego @m-usama-z