-
Notifications
You must be signed in to change notification settings - Fork 234
Add max_read_window_size config to prefetcher benchmarks
#1566
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -54,6 +54,7 @@ benchmarks: | |
|
|
||
| prefetch: | ||
| max_memory_target: !!null | ||
| max_read_window_size: !!null | ||
|
|
||
| crt: | ||
| crt_benchmarks_path: !!null | ||
|
|
@@ -62,7 +63,7 @@ benchmarks: | |
| # None | ||
|
|
||
| client_backpressure: | ||
| read_window_size: !!null #2147483648 | ||
| max_read_window_size: !!null #2147483648 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this a constant read window size or can it go up to this value? |
||
|
|
||
|
|
||
| hydra: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -218,7 +218,7 @@ struct CliArgs { | |
| #[arg( | ||
| long, | ||
| help = "Initial read window size in bytes, used to dictate how far ahead we request data from S3", | ||
| default_value = "0" | ||
| default_value = "2147483648" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My understanding is this is a fixed read window size in client benchmarks. So should we rename the parameter to read_window_size?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: can we also document here somehow that this number corresponds to 2GiB? |
||
| )] | ||
| initial_window_size: Option<usize>, | ||
| #[arg(long, help = "Output file to write the results to", value_name = "OUTPUT_FILE")] | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -92,7 +92,7 @@ pub struct CliArgs { | |
| #[arg( | ||
| long, | ||
| help = "Size of read requests requests to the prefetcher", | ||
| default_value_t = 128 * 1024, | ||
| default_value_t = 256 * 1024, | ||
| value_name = "BYTES", | ||
| )] | ||
| read_size: usize, | ||
|
|
@@ -233,9 +233,9 @@ fn main() -> anyhow::Result<()> { | |
| let received_size = received_bytes.load(Ordering::SeqCst); | ||
| total_bytes += received_size; | ||
| println!( | ||
| "{iteration}: received {received_size} bytes in {:.2}s: {:.2} Gib/s", | ||
| "{iteration}: received {received_size} bytes in {:.2}s: {:.2} Gb/s", | ||
| elapsed.as_secs_f64(), | ||
| (received_size as f64) / elapsed.as_secs_f64() / (1024 * 1024 * 1024 / 8) as f64 | ||
| (received_size as f64) / elapsed.as_secs_f64() / (1000 * 1000 * 1000 / 8) as f64 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: can we make this value more readable? not sure if best to use a clearly named variable or a function to reuse in line 251 too |
||
| ); | ||
| iter_results.push(json!({ | ||
| "iteration": iteration, | ||
|
|
@@ -246,9 +246,9 @@ fn main() -> anyhow::Result<()> { | |
| } | ||
| let total_elapsed = total_start.elapsed(); | ||
| println!( | ||
| "\nTotal: {iteration} iterations, {total_bytes} bytes in {:.2}s: {:.2} Gib/s", | ||
| "\nTotal: {iteration} iterations, {total_bytes} bytes in {:.2}s: {:.2} Gb/s", | ||
| total_elapsed.as_secs_f64(), | ||
| (total_bytes as f64) / total_elapsed.as_secs_f64() / (1024 * 1024 * 1024 / 8) as f64 | ||
| (total_bytes as f64) / total_elapsed.as_secs_f64() / (1000 * 1000 * 1000 / 8) as f64 | ||
| ); | ||
|
|
||
| if let Some(output_path) = args.output_file { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For prefetcher, we could configure initial and max window size, do we want to configure both? Would it be a like for like comparision with client backpressure benchmark if we just configure max window size?