Skip to content

docs(design): in-memory pipeline#389

Open
yulnr wants to merge 7 commits into
dial9-rs:mainfrom
yulnr:docs/in-memory-pipeline-design
Open

docs(design): in-memory pipeline#389
yulnr wants to merge 7 commits into
dial9-rs:mainfrom
yulnr:docs/in-memory-pipeline-design

Conversation

@yulnr
Copy link
Copy Markdown
Collaborator

@yulnr yulnr commented May 11, 2026

#279

Adds a design document for the implementation of a full in-memory pipeline that does not rely on writing to disk.
The last section (# 7 open questions) includes some of the items that I don't have any strong preference on.

Comment thread dial9-tokio-telemetry/design/in-memory-pipeline.md Outdated
Copy link
Copy Markdown
Contributor

@rcoh rcoh left a comment

Choose a reason for hiding this comment

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

seems pretty much good, worth a prototype

/// via [`Fs::seal`].
pub trait Fs: Send + Sync + 'static {
// --- Write side ---
fn create(&self, path: &Path) -> io::Result<Box<dyn Write + Send>>;
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.

probably fine but we should benchmark. I would not be surprised if you get significant wins from being able to optimize on the specific type in use.

Comment thread dial9-tokio-telemetry/design/in-memory-pipeline.md Outdated
@yulnr yulnr force-pushed the docs/in-memory-pipeline-design branch from 2e2c02b to b66fee8 Compare May 15, 2026 13:07
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