Skip to content

Consider a Resolver that uses tokio-threadpool::blocking instead of futures-cpupool #1676

Closed
@seanmonstar

Description

@seanmonstar

Using tokio_threadpool::blocking can reduce some overhead, and make resolving use an existing threadpool instead of needing a separate dedicated one. It can't be the default, since it only works if the executor is tokio_threadpool, whereas the futures_cpupool resolver works with any executor, but it'd be nice (and easy) to offer it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-clientArea: client.C-featureCategory: feature. This is adding a new feature.E-easyEffort: easy. A task that would be a great starting point for a new contributor.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions