-
Notifications
You must be signed in to change notification settings - Fork 216
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
Windows performance #3453
Comments
The effect of disabling stack traces on Windows:
|
stefantalpalaru
added a commit
that referenced
this issue
Mar 4, 2022
See: #3453 TODO: make libbacktrace/libunwind work in MSYS2, to get those stack traces back.
stefantalpalaru
added a commit
that referenced
this issue
Mar 5, 2022
See: #3453 TODO: make libbacktrace/libunwind work in MSYS2, to get those stack traces back.
zah
pushed a commit
that referenced
this issue
Mar 5, 2022
See: #3453 TODO: make libbacktrace/libunwind work in MSYS2, to get those stack traces back.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the stop-at-synced-epoch branch that adds the option with the same name, I did a rough benchmark of initial syncing speed on mainnet for a regular build running on Linux native and Windows inside VirtualBox:
rm -rf build/data/shared_mainnet_0; time ./run-mainnet-beacon-node.sh --web3-url="wss:https://mainnet.infura.io/ws/v3/API_TOKEN" --metrics --metrics-port=8008 --enr-auto-update --doppelganger-detection=off --num-threads=0 --stop-at-synced-epoch=100
I'm already excluding the Windows folder from Defender and VirtualBox is using hardware acceleration, KVM paravirtualisation and host I/O cache to minimise overhead.
The two main things we lack on Windows are lightweight backtraces and LTO.
The text was updated successfully, but these errors were encountered: