casper-network / casper-network/casper-node
Re-evaluate memory usage
Open
- Dominant language
- Rust
- Stars
- 399
- Forks
- 224
- Avg merge
- 15h 44m
- Merged PRs (30d)
- 2
Description
Having a look at memory usage again, ideally specify tighter lower bounds and possibly optimize some low-hanging fruits in terms of memory usage.
Potentially for this analysis a custom allocator wrapper can be used to trace and color sections of memory depending on the component.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.