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

Investigate tracemalloc #5947

Closed
pp-mo opened this issue May 9, 2024 · 1 comment · Fixed by #5948
Closed

Investigate tracemalloc #5947

pp-mo opened this issue May 9, 2024 · 1 comment · Fixed by #5948
Assignees
@pp-mo @stephenworsley

Comments

@pp-mo
Copy link
Member

pp-mo commented May 9, 2024

@pp-mo has some ideas on this

End goal: replace existing Iris memory benchmarking with a tracemalloc approach, hopefully as a basis for almost all SciTools memory benchmarking in future

Brief team discussion Thu 9th afternoon
@pp-mo pp-mo mentioned this issue May 9, 2024
Merged
@pp-mo
Copy link
Member Author

pp-mo commented May 10, 2024 •
edited

See #5946 for investigation
and #5948 for actual proposals

@trexfeathers trexfeathers linked a pull request May 13, 2024 that will close this issue
Use tracemalloc for memory measurements. #5948
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pp-mo pp-mo

@stephenworsley stephenworsley

Labels
None yet
Projects
🚴 Peloton
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use tracemalloc for memory measurements. pp-mo/iris
2 participants
@pp-mo @stephenworsley