Document micro-optimizations that should be done before final game release
Open
A-Cross-Cutting
C-Docs
C-Performance
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 161
Description
## How can Bevy's documentation be improved?
Several performance optimizations can be done just before final release, but are impractical for development.
As a starting point:
- Enabling Link Time Optimization
- Disabling dynamic linking
- Reducing or removing logging, see https://github.com/bevyengine/bevy/pull/4580
These should be documented in a single central place.
Contributor guide
Assessment
This issue has not been assessed yet.