spiffe / spiffe/spiffe-step-ssh
Memory usage
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
On a small rpi server using bootc:
# du -chs /run/spiffe/step-ssh-server/a/db/*
441M /run/spiffe/step-ssh-server/a/db/000000.vlog
265M /run/spiffe/step-ssh-server/a/db/000001.vlog
2.5M /run/spiffe/step-ssh-server/a/db/000006.sst
54M /run/spiffe/step-ssh-server/a/db/000007.sst
54M /run/spiffe/step-ssh-server/a/db/000008.sst
54M /run/spiffe/step-ssh-server/a/db/000009.sst
54M /run/spiffe/step-ssh-server/a/db/000010.sst
4.0K /run/spiffe/step-ssh-server/a/db/KEYREGISTRY
4.0K /run/spiffe/step-ssh-server/a/db/LOCK
4.0K /run/spiffe/step-ssh-server/a/db/MANIFEST
922M total
Can get quite large compared to the small amount of ram available.
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 report names no source file, test, or database implementation. Start by reproducing the database growth on the small Raspberry Pi server and trace which component creates the listed files. The issue does not define a target resource limit or a specific fix, so completion criteria need to be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, raspberry-pi
- Domain
- database, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100