-
Notifications
You must be signed in to change notification settings - Fork 7
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
added error messages and memory reset #53
Conversation
johncalesp
commented
May 8, 2023
- Added external method to clear cache in GPU memory
- Added error codes for habitat and energy in protobuf
- Modified try-except blocks for habitat and energy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd call this file memory_utils or something similar
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
renamed to utils.py
@@ -150,47 +150,56 @@ def energy_compute(self) -> pm.EnergyResponse: | |||
for _ in range(iterations): | |||
iteration(*inputs) | |||
energy_measurer.end_measurement() | |||
resp.total_consumption = energy_measurer.total_energy()/float(iterations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this change mean a user has to enable CPU monitoring to get energy measurements? What if a user doesn't have access like in cloud instances?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually no, the code is the same as before. I tried on my PC removing access to pyRAPL and the profile will only measure GPU power consumption.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After looking over the code with John, we determined that the exception is already handled in the measurement
deepview_profile/analysis/session.py
Outdated
logger.error(message) | ||
resp.analysis_error.error_message = message | ||
except: | ||
logger.error("There was an error running deepview predict") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change "deepview predict" to "DeepView Predict"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got it
Code Climate has analyzed commit dd97ec6 and detected 0 issues on this pull request. View more on Code Climate. |