Skip to content

concurrent dsp functions #8

@stagas

Description

@stagas

not sure how it can be executed but it would be nice to have run different dsp functions concurrently.

benefits of this would be that each dsp would run on a different worker, therefore utilizing all the cores, plus the state would only reset for the function you're currently editing, the rest could keep their state.

one way to execute this would be for the engine to consider all exports as dsp functions, create a worker for each and evaluate a different one on each worker. then when editing, we can find out which function was edited, and if it's one of the exports, just re-eval that worker, not the entire thing. to reset every worker you would just need to do an edit in the upper(topmost) level. this is maybe too implicit though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions