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

Jump to bottom

chunk allocation during serialization does not use memory pool/allocator chunk size #1424

Closed
biddisco opened this issue Mar 24, 2015 · 1 comment
Closed

chunk allocation during serialization does not use memory pool/allocator chunk size #1424

biddisco opened this issue Mar 24, 2015 · 1 comment
Assignees
@biddisco
Labels
affecting: CSCS category: parcel transport type: enhancement
Milestone
0.9.11

Comments

@biddisco
Copy link
Contributor

Excessive memory allocation request occur during serialization. the traits get_type_size does not appear to return the correct size so memory use grows steadily as each parcel is serialized. By making use of the allocator chunk size, this cost can be significantly offset.
@biddisco biddisco self-assigned this Mar 24, 2015
@hkaiser hkaiser added this to the 0.9.11 milestone Mar 25, 2015
@biddisco biddisco reopened this Mar 25, 2015
@biddisco biddisco mentioned this issue Mar 25, 2015
Merged
@hkaiser
Copy link
Member

hkaiser commented Mar 29, 2015

@biddisco: Can this be closed now (after #1425 was merged)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@biddisco biddisco

Labels
affecting: CSCS category: parcel transport type: enhancement
Projects
None yet
Milestone
0.9.11
Development

No branches or pull requests
2 participants
@hkaiser @biddisco