Skip to content

Fibers PoC#144

Draft
torsteingrindvik wants to merge 1 commit intonagisa:mainfrom
torsteingrindvik:fibers-test
Draft

Fibers PoC#144
torsteingrindvik wants to merge 1 commit intonagisa:mainfrom
torsteingrindvik:fibers-test

Conversation

@torsteingrindvik
Copy link
Copy Markdown

@torsteingrindvik torsteingrindvik commented Aug 29, 2025

It's not pretty (the Rust code I mean)- I just wanted to see what it looked like.

image

EDIT: I whoopsed the location of the join prints, nvm them

image

One strange thing is that it reports finishing after negative time:

image

The example follows section "3.10 Fiber" of the Tracy manual. Kinda. Added some subspans just to see things nest well.

All in all I think this is interesting- doing this properly could allow having Rust work sent across threads properly tracked. Not sure how it looks in a real life complex app with lots and lots of spans though.

Opening up in case someone wants to try/discuss. I don't intend to do anything more at the moment.

Signed-off-by: Torstein Grindvik <torstein.grindvik@muybridge.com>
@torsteingrindvik torsteingrindvik mentioned this pull request Aug 30, 2025
@nagisa
Copy link
Copy Markdown
Owner

nagisa commented Jan 5, 2026

Thank you for experimenting with this. Fiber-based visualization is definitely desirable for Rust, especially async and tracing integration. Unfortunately the profiling perf impact simply by enabling fiber feature is so severe that I never really pursued it further. It definitely is not something that we could enable by default, and that alone requires a lot of design work, unfortunately.

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