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.

Sign up for GitHub

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

Enable LTO in Rust release profile #32

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Enable LTO in Rust release profile #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1dc368c
enabled lto in drasi-core
ruokun-niu Oct 28, 2024
34ddf94
updated perf test shell script to use release profile
ruokun-niu Oct 28, 2024
d2dbaff
perf readme
ruokun-niu Oct 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@ version = "0.2.0"

[profile.release]
codegen-units = 1
lto = "thin"
lto = true
4 changes: 2 additions & 2 deletions query-perf/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@ This allows us to establish a baseline understanding of raw component performanc
The tool is structured around the concept of a Performance Test Scenario, which represents the combination of a specific Continuous Query against a data model. The same Performance Test Scenario with the same expected outcomes can then be run against different component configurations simply by specifying the desired component configuration using command line parameters.

# Execution
You can run the The Component Performance Test Tool from a compiled binary:
You can run the The Component Performance Test Tool using a shell script:

```
./query-perf <ARGS>
./run_perf_tests.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ruokun-niu this change is not correct. This text talks about running the component test tool in general, this script just runs the tool using our set of pre-configured tests. Need to revert.

```

... or using the Cargo tool from the project directory:
Expand Down
15 changes: 0 additions & 15 deletions query-perf/run_perf_tests
View file
Open in desktop

This file was deleted.

24 changes: 24 additions & 0 deletions query-perf/run_perf_tests.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
#!/bin/bash

# Define the output file
output_file="all_output_lto.txt"

# Clear the output file if it already exists
> "$output_file"

# Run each command and append its output to the output file
cargo run --release -- -s single_node_property_projection -e memory -r memory --seed 12345 >> "$output_file"
cargo run --release -- -s single_node_property_projection -e rocksdb -r rocksdb --seed 12345 >> "$output_file"
cargo run --release -- -s single_node_property_projection -e redis -r redis --seed 12345 >> "$output_file"

cargo run --release -- -s single_node_calculation_projection -e memory -r memory --seed 12345 >> "$output_file"
cargo run --release -- -s single_node_calculation_projection -e rocksdb -r rocksdb --seed 12345 >> "$output_file"
cargo run --release -- -s single_node_calculation_projection -e redis -r redis --seed 12345 >> "$output_file"

cargo run --release -- -s single_path_averaging_projection -e memory -r memory --seed 12345 >> "$output_file"
cargo run --release -- -s single_path_averaging_projection -e rocksdb -r rocksdb --seed 12345 >> "$output_file"
cargo run --release -- -s single_path_averaging_projection -e redis -r redis --seed 12345 >> "$output_file"

cargo run --release -- -s single_path_no_change_averaging_projection -e memory -r memory --seed 12345 >> "$output_file"
cargo run --release -- -s single_path_no_change_averaging_projection -e rocksdb -r rocksdb --seed 12345 >> "$output_file"
cargo run --release -- -s single_path_no_change_averaging_projection -e redis -r redis --seed 12345 >> "$output_file"
Loading