Want to understand why reducing value of opt_lg_chunk is reducing the total size of the process
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.2k
- Forks
- 1.6k
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 13
Description
I have the below statistics for my process with opt_lg_chunk values of 14, 16 ,18 ,20 and 22.
legacy/task_memory_internals.txt: 9110 root 4 0 137M 56628K kqread 0:03 0.00% rpd
lg_chunk_14/task_memory_internals_14.txt: 3809 root 4 0 141M 60524K kqread 0:04 0.00% rpd
lg_chunk_16/task_memory_internals_16.txt: 3862 root 4 0 145M 58892K kqread 0:04 0.00% rpd
lg_chunk_18/task_memory_internals_18.txt: 3806 root 4 0 148M 57472K kqread 0:04 0.00% rpd
lg_chunk_20/task_memory_internals_20.txt: 3826 root 4 0 151M 56892K kqread 0:03 0.00% rpd
lg_chunk_22/task_memory_internals_22.txt: 3816 root 4 0 153M 57332K kqread 0:10 0.00% rpd
Please let me know what contributes to the change in size of the process of rpd when the opt_lg_chunk change happens in my above example.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the measurements in legacy/task_memory_internals.txt and the lg_chunk_14 through lg_chunk_22 task_memory_internals files, then trace where opt_lg_chunk is defined and used. Determine which allocator behavior accounts for the process-size differences. Done means a documented explanation tied to the reported measurements, with any needed reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100