[GCP] Assess the impact of logging verbosity on binary performance
@phbnf is already working on this.
Since Mar 9, 2026.
Assessment
This issue has not been assessed yet.
Description
Let's see if reducing logging verbosity makes the binary more efficient or not.
Then, adjust the logging verbosity accordingly.
- Dominant language
- Go
- Stars
- 37
- Forks
- 18
- Avg merge
- 19h 22m
- Merged PRs (30d)
- 15
Contributor guide
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.
More from transparency-dev/tesseract
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
transparency-dev/tesseract#879 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
transparency-dev/tesseract#851 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 68/100
transparency-dev/tesseract#937 ·
-
bug
transparency-dev/tesseract#918 · 1 comment · 1 assignee ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
transparency-dev/tesseract#901 ·
All issues in transparency-dev/tesseract
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100