Skip to content

Add Data Track benchmarking examples#1039

Merged
chenosaurus merged 7 commits intomainfrom
dc/data_track_benchmarking_examples
Apr 28, 2026
Merged

Add Data Track benchmarking examples#1039
chenosaurus merged 7 commits intomainfrom
dc/data_track_benchmarking_examples

Conversation

@chenosaurus
Copy link
Copy Markdown
Contributor

add /examples/data_track_benchmarking apps to measure data track throughput, latency, and delivery rate.

@chenosaurus chenosaurus requested review from 1egoman and ladvoc April 22, 2026 23:42
Copy link
Copy Markdown
Contributor

@ladvoc ladvoc left a comment

Choose a reason for hiding this comment

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

LGTM ✅

Comment thread examples/data_track_benchmark/src/main.rs Outdated
Comment thread examples/data_track_benchmark/src/main.rs Outdated
Copy link
Copy Markdown
Contributor

@stephen-derosa stephen-derosa left a comment

Choose a reason for hiding this comment

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

lgtm, but definetly not a rust expert!

Comment thread examples/data_track_benchmark/README.md
@@ -0,0 +1,393 @@
use anyhow::Result;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: copyright

}

let mut df = df! [
"size_kb" => col_size_kb,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

do we expect data tracks to perform uniformly for varying sizes? I.e. is there any need to make size_kb = size_kb +/- size_noise

@chenosaurus chenosaurus merged commit 2d2d57b into main Apr 28, 2026
23 checks passed
@chenosaurus chenosaurus deleted the dc/data_track_benchmarking_examples branch April 28, 2026 21:00
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.

3 participants