Make it possible to run without bringing a Tokio Runtime

[rcoh]

To work in applications that don't use Tokio, it should either support running its own current-thread runtime to drive the futures.

[arielb1]

Running the AWS reporter without a Tokio runtime is going to be a pain.

It does make some sense to allow the rest of it to run without Tokio.

[rcoh]

Doesn't need to run without Tokio, but it needs to not require the caller to bring it themselves, in my opinion.

e.g. it could, as a configurable option, manage a 2 worker runtime independently.

[arielb1]

e.g. it could, as a configurable option, manage a 2 worker runtime independently.

1 worker is enough.

The main issue is that if you want to use AWS credentials, you need to run your own code within Tokio runtime anyway to do credentials manipulation.

I think that a mode that spawns a Tokio runtime basically just to use a LocalReporter is not composable enough. OTOH documentation to tell people to use a local runtime is probably good.

[rcoh]

There are some bugs with Hyper on a single worker runtime that I believe still exist.

…

On Sun, Sep 21, 2025, 8:59 AM Ariel Ben-Yehuda ***@***.***> wrote: *arielb1* left a comment (async-profiler/rust-agent#96) <#96 (comment)> e.g. it could, as a configurable option, manage a 2 worker runtime independently. 1 worker is enough. The main issue is that if you want to use AWS credentials, you need to pre-warm a Tokio runtime anyway to do credentials manipulation. I think that a mode that spawns a Tokio runtime basically just to use a LocalReporter is not composable enough. OTOH documentation to tell people to use a local runtime is probably good. — Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADYKZZDWUSCDEK6KV72Q533T2OMNAVCNFSM6AAAAACGV3DV3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJVHE4DANRUGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[arielb1]

There are some bugs with Hyper on a single worker runtime

What sort of bugs?

[rcoh]

awslabs/aws-sdk-rust#440

[arielb1]

awslabs/aws-sdk-rust#440

Do we actually know what's going on there? Is it possible that it is caused by users that have blockage in their runtimes?