Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use maxperf profile when building Lighthouse from source #1452

Merged
merged 1 commit into from
Jul 25, 2023

Conversation

jimmygchen
Copy link
Contributor

Lighthouse official binaries & images are built using the maxperf profile to enable further optimizations, so it might be worth changing the Dockerfile for source builds to use the same, depending on what user uses the source build feature for - if using it for comparative testing with stable or running a validator, it probably makes sense to enable maxperf.

From Lighthouse book:

maxperf: default for binary releases, enables aggressive optimisations including full LTO. Although compiling with this profile improves some benchmarks by around 20% compared to release, it imposes a significant cost at compile time and is only recommended if you have a fast CPU.

@yorickdowne yorickdowne merged commit 2854a2a into eth-educators:main Jul 25, 2023
7 checks passed
@gitpoap-bot
Copy link

gitpoap-bot bot commented Jul 25, 2023

Congrats, your important contribution to this open-source project has earned you a GitPOAP!

GitPOAP: 2023 eth-docker Contributor:

GitPOAP: 2023 eth-docker Contributor GitPOAP Badge

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.

@jimmygchen jimmygchen deleted the build-lh-with-maxperf branch July 25, 2023 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants