gwsystems / gwsystems/sledge-serverless-framework
Memory footprint logging
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 124
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
The base is now missing logging mechanism for the memory overhead for sandboxes. We had that in the past at some point, now we don't. I am guessing @bushidocodes had to take it away when the obj-pools were added?
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
The issue names no files, tests, or entry points. Start by locating the sandbox memory and obj-pool code and any existing logging, then use repository history to find the previous memory-overhead mechanism. Done means the base again reports sandbox memory overhead through logging, with coverage in the relevant tests if they exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- observability, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100