-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Add Micro-benchmark for iter_torch_batches #50230
Conversation
Signed-off-by: Srinath Krishnamachari <[email protected]>
@@ -0,0 +1,204 @@ | |||
import time |
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.
@bveeramani @raulchen what's the canonical place for us to harbor benchmarks? Ideally we'd want to capture this at go/data-perf
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.
Canonical place is release/nightly_tests/dataset/
.
Btw, there's already a benchmark for iter_torch_batches
ray/release/release_data_tests.yaml
Lines 235 to 246 in f992321
- name: iter_torch_batches | |
cluster: | |
cluster_compute: autoscaling_gpu_compute.yaml | |
run: | |
timeout: 2400 | |
script: > | |
python read_and_consume_benchmark.py | |
s3://air-example-data-2/100G-image-data-synthetic-raw/ --format image | |
--iter-torch-batches | |
for i in range(iterations): | ||
start_time = time.perf_counter() | ||
if verbose: | ||
logger.info(f"[Iteration {i+1}] Start") | ||
|
||
for _ in dataset.iter_torch_batches( | ||
batch_size=batch_size, | ||
collate_fn=collate_fn, | ||
prefetch_batches=prefetch_batches, | ||
local_shuffle_buffer_size=local_shuffle_buffer_size, | ||
local_shuffle_seed=local_shuffle_seed, | ||
): | ||
pass |
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.
Let's add a warm-up phase as well
Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.