Skip to content

Add incremental upload stress test - #1908

Open
Priyankakarumuru1 wants to merge 1 commit into
awslabs:feature/memory-limitfrom
Priyankakarumuru1:incremental-upload-stress-test
Open

Add incremental upload stress test#1908
Priyankakarumuru1 wants to merge 1 commit into
awslabs:feature/memory-limitfrom
Priyankakarumuru1:incremental-upload-stress-test

Conversation

@Priyankakarumuru1

@Priyankakarumuru1 Priyankakarumuru1 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Added a new stress test for incremental uploads. The test has 48 workers that write 100 MiB objects concurrently using incremental upload mode while sharing a 512 MiB memory limit. This mirrors the existing sustained_writes scenario but with the incremental upload path enabled.

Does this change impact existing behavior?

No. This only adds a new test

Does this change need a changelog entry? Does it require a version change?

No. Test-only change


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

pub chunk: usize,
}

impl Worker for IncrementalWriter {

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.

This is exactly the same as our existing Writer? we should re-use to avoid duplication.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good point! I created it separately for clearer observability (incremental_writer vs writer in logs/metrics), but you're right - will reuse Writer to avoid the duplication.

# (credential-chain probes, 404 heads, CRT ERROR on recoverable conditions) that would
# dominate a long run's CI log without signaling a real failure.
RUST_LOG: "warn,stress_tests=info,awscrt=off"
S3_BUCKET_NAME: ${{ vars.S3_BENCH_BUCKET_NAME }}

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.

This needs to be changed to S3 express bucket? Check how benchmark CI is configured for S3 Express runs as a reference

RUST_LOG: "warn,stress_tests=info,awscrt=off"
S3_BUCKET_NAME: ${{ vars.S3_BENCH_BUCKET_NAME }}
S3_BUCKET_TEST_PREFIX: ${{ vars.S3_BUCKET_BENCH_PREFIX || 'mountpoint-benchmark/' }}
S3_ENDPOINT_URL: ${{ vars.S3_BENCH_ENDPOINT_URL }}

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.

Presumably this as well?

@@ -0,0 +1,40 @@
//! `incremental_upload`: 32 workers concurrently writing 64 MiB objects using incremental upload

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.

Let's just duplicate existing sustained_writes scenario (same parameters/settings - just do incremental upload flag/config). And name it like sustained_writes_incremental_upload (for consistency with benchmark naming)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done! Matched sustained_writes exactly - same parameters, just added incremental_upload: true config.

Signed-off-by: Priyankakarumuru1 <prikaru@amazon.com>
@Priyankakarumuru1
Priyankakarumuru1 force-pushed the incremental-upload-stress-test branch from ce8e44e to b412a64 Compare July 29, 2026 15:06
@Priyankakarumuru1
Priyankakarumuru1 deployed to PR integration tests July 29, 2026 15:06 — with GitHub Actions Active
@Priyankakarumuru1
Priyankakarumuru1 marked this pull request as ready for review July 29, 2026 16:26
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.

2 participants