tensorflow / tensorflow/tensorboard
Enable Link-Time Optimization (LTO) and evaluate other optimizations for TensorBoard
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
Hi!
Recently I read the design document about some design choices and performance-oriented questions. I want to suggest several optimization techniques that can improve the project performance further.
I noticed that in the Cargo.toml file for the Rust part Link-Time Optimization (LTO) is not enabled. I suggest enabling it since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance.
I suggest enabling LTO only for the Release builds to not sacrifice the developers' experience during the working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional release-lto profile where additionally to regular release optimizations LTO also will be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most performant version of the application.
After applying LTO I can suggest evaluating other optimization options like evaluating Profile-Guided Optimization (PGO) (more materials and benchmarks are available at my repo: https://github.com/zamazan4ik/awesome-pgo) and Post-Link Optimization (PLO) with tools like LLVM BOLT.
Thank you.
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
Read docs/design/rustboard.md and tensorboard/data/server/Cargo.toml first. Check how release profiles are configured, then assess the proposed release-only LTO change and the suggested PGO or LLVM BOLT evaluation; done means the optimization approach is selected and its performance or binary-size impact is evaluated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100