Skip to content

[New Physical IO] Migrating new design with Blob#294

Merged
ozkoca merged 19 commits intoawslabs:physical-iofrom
ozkoca:physical-io-test
Jun 26, 2025
Merged

[New Physical IO] Migrating new design with Blob#294
ozkoca merged 19 commits intoawslabs:physical-iofrom
ozkoca:physical-io-test

Conversation

@ozkoca
Copy link
Collaborator

@ozkoca ozkoca commented Jun 20, 2025

Description of change

This PR merges the new PhysicalIO changes to the Blob object and start to use the new implementation.

Next Steps:

  • Range coalescing implementation
  • Retry policy implementation

Relevant issues

PR History:

#286
#287
#288
#289

Does this contribution introduce any breaking changes to the existing APIs or behaviors?

No

Does this contribution introduce any new public APIs or behaviors?

No

How was the contribution tested?

Unit test

Does this contribution need a changelog entry?

n/A


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).

@ozkoca ozkoca changed the title [INPROGRESS] [New Physical IO] Migrating new design with Blob [New Physical IO] Migrating new design with Blob Jun 25, 2025
@ozkoca ozkoca merged commit e6e665b into awslabs:physical-io Jun 26, 2025
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jun 26, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

awslabs#286
awslabs#287
awslabs#288
awslabs#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jun 26, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

awslabs#286
awslabs#287
awslabs#288
awslabs#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jun 26, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

awslabs#286
awslabs#287
awslabs#288
awslabs#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
ozkoca added a commit that referenced this pull request Jun 26, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

#286
#287
#288
#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jun 26, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

awslabs#286
awslabs#287
awslabs#288
awslabs#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jun 26, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

awslabs#286
awslabs#287
awslabs#288
awslabs#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
@ozkoca ozkoca mentioned this pull request Jun 30, 2025
1 task
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jul 14, 2025
This PR merges the new PhysicalIO changes to the Blob object and start
to use the new implementation.

Next Steps:
- Range coalescing implementation
- Retry policy implementation

PR History:

awslabs#286
awslabs#287
awslabs#288
awslabs#289

existing APIs or behaviors?
No

No
Unit test

n/A

---

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)](https://developercertificate.org/).
@ozkoca ozkoca deleted the physical-io-test branch July 14, 2025 16:08
ozkoca added a commit that referenced this pull request Jul 24, 2025
## Description of change
This PR adds the capability of retry to the new PhysicalIO 

#### Relevant issues
#286
#287
#288
#289
#294
#316

#### Does this contribution introduce any breaking changes to the
existing APIs or behaviors?
No

#### Does this contribution introduce any new public APIs or behaviors?
No

#### How was the contribution tested?
Unit tests


---

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)](https://developercertificate.org/).
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jul 25, 2025
Added iostats get request callback to streamReader (awslabs#317)

This PR moves IOStat callback method request from Block to StreamReader.
Needs to be done as part of code rebase

---

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)](https://developercertificate.org/).

Telemetry support for physical IO (awslabs#318)

This PR adds telemetry measures for StreamReader and BlockManager.

Introducing retry policy to new PhysicalIO (awslabs#320)

This PR adds the capability of retry to the new PhysicalIO

awslabs#286
awslabs#287
awslabs#288
awslabs#289
awslabs#294
awslabs#316

existing APIs or behaviors?
No

No

Unit tests

---

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)](https://developercertificate.org/).
ozkoca added a commit to ozkoca/analytics-accelerator-s3 that referenced this pull request Jul 25, 2025
Added iostats get request callback to streamReader (awslabs#317)

This PR moves IOStat callback method request from Block to StreamReader.
Needs to be done as part of code rebase

---

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)](https://developercertificate.org/).

Telemetry support for physical IO (awslabs#318)

This PR adds telemetry measures for StreamReader and BlockManager.

Introducing retry policy to new PhysicalIO (awslabs#320)

This PR adds the capability of retry to the new PhysicalIO

awslabs#286
awslabs#287
awslabs#288
awslabs#289
awslabs#294
awslabs#316

existing APIs or behaviors?
No

No

Unit tests

---

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)](https://developercertificate.org/).
ozkoca added a commit that referenced this pull request Jul 25, 2025
## Description of change
This PR rebases ant integrates the changes in PR
#321

#### Relevant issues
#286
#287
#288
#289
#294
#316
#320

#### Does this contribution introduce any breaking changes to the
existing APIs or behaviors?
No

#### Does this contribution introduce any new public APIs or behaviors?
No

#### How was the contribution tested?
Unit tests


---

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)](https://developercertificate.org/).
ozkoca added a commit that referenced this pull request Jul 25, 2025
## Description of change
This PR changes default read buffer size to 128KB to have a better
performance

#### Relevant issues
#286
#287
#288
#289
#294
#316
#320
#323

#### Does this contribution introduce any breaking changes to the
existing APIs or behaviors?
No

#### Does this contribution introduce any new public APIs or behaviors?
No

#### How was the contribution tested?
Unit tests

#### Does this contribution need a changelog entry?
N/A

---

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)](https://developercertificate.org/).
@ozkoca ozkoca mentioned this pull request Jul 25, 2025
1 task
ozkoca added a commit that referenced this pull request Jul 31, 2025
## Description of change
This PR implements a new PhysicalIO design with key improvements:

**Fixed Block Size:** Previously, block sizes varied based on request
ranges, requiring entire request ranges to complete before blocks became
available. The new design uses fixed-size blocks that become ready as
soon as individual blocks are filled, enabling faster data access and
better parallelization.

**Direct Block Writing:** Eliminates an extra memory copy by writing S3
data directly into Block storage instead of copying from intermediate
buffers, reducing memory overhead and CPU usage.

**Improved Concurrency:** Fixed-size blocks allow multiple blocks to be
processed independently, improving throughput for concurrent read
operations.

**Better Memory Management:** Predictable block sizes enable more
efficient memory allocation and cache management strategies.

**Enhanced Read Performance:** Blocks become available for reading as
soon as they're filled, rather than waiting for entire request ranges to
complete, reducing read latency.

#### Relevant issues
#286
#287
#288
#289
#294
#316
#320
#323
#324

#### Does this contribution introduce any breaking changes to the
existing APIs or behaviors?
No

#### Does this contribution introduce any new public APIs or behaviors?
No

#### How was the contribution tested?
Unit tests, microbenchmarks

#### Does this contribution need a changelog entry?
- [ ] I have updated the CHANGELOG or README if appropriate

---

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)](https://developercertificate.org/).
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.

1 participant