Skip to content

[otel-arrow-rust] Investigate performance trade-offs of stream based approach vs yeilding in pipeline #479

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

Open
albertlockett opened this issue May 22, 2025 · 0 comments

Comments

@albertlockett
Copy link
Member

This is motivated by a discussion here:
#455 (comment)

If we have long, synchronous blocks of code that run at some stage of the pipeline, it will block one of the worker threads, possibly for longer than we want.

One approach to this, is to make the synchronous block async and yield during the execution.

Another approach would be to break up one large batch into smaller batches, and call the synchronous code asynchronously for each batch in a stream, and reassemble the bactches at completion.

We should evaluate both these options in the future

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

No branches or pull requests

1 participant