orbiternassp / orbiternassp/NASSP
Improve DEBUG build performance
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 213
- Forks
- 74
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
Right now a lot of information is logged and printed when running a debug build.
This results in a huge performance drop.
We should evaluate everything that's turned on in a debug build and determine if it's still useful to us. Some stuff can be taken out completely or have some additional conditions before it gets compiled in or executed.
For example we could turn debug logging on per subsystem instead of everything all at once.
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.
Research direction
The issue names no files, tests, or entry points. Start by auditing what logging, printing, and other debug-only work is enabled in a DEBUG build, then assess each subsystem's usefulness and performance impact. Done means unnecessary debug work is removed or conditionally enabled, with a clear per-subsystem approach documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100