In C++ iostreams are designed very poorly and as a result they create many copies of data and extremely slow (and require 2x-4x of memory they could require!). The number of copies any IO code performs is the only really important thing. I thought that in Rust, tokio::io::AsyncWrite / tokio::io::Fi…

You cannot control the amount of copies inside the AWS library you are using, so your goal should be to reduce the number of copies that are introduced due to your choices. Using the same IO trait as the underlying library will enable you to avoid introducing extra copies. As for "the issue in Toki…

Zero-copy async IO in Rust?

help

jjpe February 18, 2024, 1:33pm 3

Then I'm curious, what about io_uring? That's designed to be async.

As an aside, it's quite remarkable that Tokio hasn't rebased to use that natively yet.

2 Likes

Topic		Replies	Views
(async) zero-copy file write() in Rust help	5	259	July 30, 2024
Spinning my wheels writing a runtime-agnostic async Rust library help	6	937	October 28, 2023
Async pwrite equivalent	4	554	May 14, 2023
Design & impl of async runtime?	3	1043	May 8, 2022
When we say async IO, what part is really "async"? help	13	2361	May 1, 2020

Zero-copy async IO in Rust?

Related topics