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

#123 Implement memory footprint mode #124

Merged
merged 16 commits into from
Sep 17, 2020
Merged

Conversation

cz4rs
Copy link
Contributor

@cz4rs cz4rs commented Sep 2, 2020

fixes #123

@cz4rs
Copy link
Contributor Author

cz4rs commented Sep 3, 2020

note:
pushing some code here, but it's definitely still work-in-progress (requires improved naming (!) and docs, reduced code duplication, independence from serialize / separate operator, implementation for other containers etc.)

@cz4rs cz4rs force-pushed the 123-memory-footprint-mode branch 14 times, most recently from 8f35f3f to 63c2320 Compare September 8, 2020 15:35
@cz4rs cz4rs force-pushed the 123-memory-footprint-mode branch 14 times, most recently from 7670e00 to a279ef5 Compare September 9, 2020 23:20
@cz4rs cz4rs force-pushed the 123-memory-footprint-mode branch from e49cab2 to fbd870c Compare September 15, 2020 17:38
@cz4rs cz4rs force-pushed the 123-memory-footprint-mode branch 2 times, most recently from 5c7a3ee to b73b4ea Compare September 15, 2020 23:45
Implement a function and a mode for measuring total memory footprint of
an object.

- use existing 'serialize' infrastructure
- add implementation and tests for std::unique_ptr, std::string, std::vector
- adjust serialization code for Footprinting mode
- add unit tests for measuring memory footprint of standard containers
- fix compiler warning in traversal test
- do not size underlying 'struct FILE' when footprinting FILE* pointer
- simplify queue serialization to avoid copying
- fix grammar typo
@cz4rs cz4rs force-pushed the 123-memory-footprint-mode branch from b73b4ea to 5c16a23 Compare September 16, 2020 10:51
@cz4rs
Copy link
Contributor Author

cz4rs commented Sep 16, 2020

@PhilMiller @lifflander if this looks ok for you, I would like to get it merged to have better CI feedback in DARMA-tasking/vt#1013

(I would be adding support for kokkos types and ironing out any discovered bugs in a subsequent PR)

@cz4rs
Copy link
Contributor Author

cz4rs commented Sep 16, 2020

@lifflander @PhilMiller (thanks for the review!)
regarding the merge permissions / protected branches: please take a look at the screenshot below, I cannot merge this pull request myself

I don't have a fresh example from vt repository, but it looked pretty similar there (we discussed this some time ago on DARMA technical meeting)

image

@lifflander
Copy link
Contributor

lifflander commented Sep 17, 2020

@lifflander @PhilMiller (thanks for the review!)
regarding the merge permissions / protected branches: please take a look at the screenshot below, I cannot merge this pull request myself

I believe that I have fixed this now for this repository.

@lifflander lifflander merged commit 7c8115e into develop Sep 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement memory footprint mode
3 participants