Skip to content

Expose thread-local APIs when possible #216

Description

@itamarst

Given the existence in the wild (e.g. in scikit-learn) of nested Python thread pools, being able to set limits per-thread is that much more important for reliable oversaturation prevention.

Some libraries provide both process-wide and thread-local settings:

In practice BLIS is probably not viable.

Long-term, I think there should be a ecosystem-wide push to provide thread-local APIs.

In the short term, exposing MKL at least would be helpful for #215.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions