-
Notifications
You must be signed in to change notification settings - Fork 0
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
New crate: apply a user-supplied function to a Stream
of buffers
#26
Comments
But remember that, per chunk, we want all processing to happen in one go, so that the data for that chunk is still in cpu cache. Instead of a compression crate, Maybe make a "datastream" crate. The user provides a processing function (which might include compression). And the crate runs that function in a rayon thread pool. The crate could still provide hooks for common compression libs. Or maybe that should be another crate |
Stream
of buffers
And maybe make a wrapper which can pull UPDATE: See #107 |
Stream
of buffersStream
of buffers
This issue is superseded by #106 |
Each item will be a
User data is required to allow users to identify the buffers after they've been compressed because the order might change
Update: Framed might already do this: https://docs.rs/async-codec/latest/async_codec/
Related
object_store
to read data from cloud object storage, perhaps using an adaptor which convertsobject_store
to a channel of data chunks.todo
The text was updated successfully, but these errors were encountered: