-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
Incorrect reported estimate/used memory with GPU solver #173
Comments
I've implemented some reporting of the memory that is used on the GPU after the simulation has run - For smaller models the reported memory usage (using plutil 'Resident Set Size') does vary from run to run and depending (I think) on the machine also. I'd be grateful for some feedback. |
Many articles suggest using 'Unique Set Size' as a measure for memory usage unique to the current process. I was wondering how you have decided the value of Also, |
@spaceVStab thanks, I see http://grodola.blogspot.com/2016/02/psutil-4-real-process-memory-and-environ.html, I will change I will look into |
I think this is an error with how the memory usage is being reported when run with the solver on GPU, i.e. it is not the estimated memory that is wrong, rather the reported actual usage. At the moment we use the psutil module with the memory info function (https://psutil.readthedocs.io/en/latest/#psutil.Process.memory_info). If anyone can recommend a better method please let me know, especially for returning GPU used memory.
The text was updated successfully, but these errors were encountered: