You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is this task and why do we need to work on it?
To help to answer why are we not getting better throughput/latency, we want to do flamegraphing for some runs.
What work will need to be done to complete this task?
Write scripts to generate flamegraph automatically.
Are there any other details to include?
If you want to profile the code, it's not too hard to set up, you would just hook it up to here: https://github.com/flamegraph-rs/flamegraph?tab=readme-ov-file#installation and make sure you copy the RUSTFLAGS from the justfile when running.
You would end up with a command like RUSTFLAGS='--cfg async_executor_impl="async-std" --cfg async_channel_impl="async-std"' sudo cargo flamegraph --test TEST_NAME.
If it's a cargo subcommand you can do just cargo flamegraph (defaults to async-std).
[Copy-Pasted from Zulip]
What are the acceptance criteria to close this issue?
Flamegraphing is integrated into the scripts or could be easily run when we want one for a benchmark run.
Branch work will be merged to (if not the default branch)
No response
The text was updated successfully, but these errors were encountered:
What is this task and why do we need to work on it?
To help to answer why are we not getting better throughput/latency, we want to do flamegraphing for some runs.
What work will need to be done to complete this task?
Write scripts to generate flamegraph automatically.
Are there any other details to include?
If you want to profile the code, it's not too hard to set up, you would just hook it up to here: https://github.com/flamegraph-rs/flamegraph?tab=readme-ov-file#installation and make sure you copy the RUSTFLAGS from the justfile when running.
You would end up with a command like
RUSTFLAGS='--cfg async_executor_impl="async-std" --cfg async_channel_impl="async-std"' sudo cargo flamegraph --test TEST_NAME
.If it's a cargo subcommand you can do
just cargo flamegraph
(defaults toasync-std
).[Copy-Pasted from Zulip]
What are the acceptance criteria to close this issue?
Flamegraphing is integrated into the scripts or could be easily run when we want one for a benchmark run.
Branch work will be merged to (if not the default branch)
No response
The text was updated successfully, but these errors were encountered: