You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "Xuanwo (via GitHub)" <gi...@apache.org> on 2026/09/09 06:22:51 UTC

Re: [I] tracking: improve Python binding I/O performance [opendal]

Xuanwo commented on issue #8159:
URL: https://github.com/apache/opendal/issues/8159#issuecomment-5596949471

   Follow-up on the remaining blocking File GIL work, checked against `4b132b0d33c8a5b84ff83f6fcfbab264860c5b3d`:
   
   #8180 already added `Python::detach` to blocking Operator I/O. The original statement that the binding has no detach path is therefore historical. `File.read`, `File.write`, and writer close still enter blocking I/O without detaching. This remaining work is already covered by this tracking issue; no duplicate GIL issue is needed.
   
   [File implementation](https://github.com/apache/opendal/blob/4b132b0d33c8a5b84ff83f6fcfbab264860c5b3d/bindings/python/src/file.rs) and [Operator implementation](https://github.com/apache/opendal/blob/4b132b0d33c8a5b84ff83f6fcfbab264860c5b3d/bindings/python/src/operator.rs).
   
   The proposed scope is to release the GIL while safely waiting for File storage I/O, preserving File state exclusion and input ownership. Borrowed writable buffers such as `readinto` need their own safety analysis; detaching around an exposed raw buffer is not automatically safe. A deterministic test should verify that an unrelated Python thread progresses during a blocked File operation on GIL-enabled CPython.
   
   This is a source-confirmed optimization opportunity. The benchmark does not isolate its throughput contribution, and it cannot explain the async upload gap. Rust network tasks may continue while the calling Python thread holds the GIL; the claim is about other Python threads, not serialization of all network traffic.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org