Skip to content

Fast special cases for MonteCarlo #10

@JADekker

Description

@JADekker

In the current implementation, I believe every MonteCarlo problem gets mapped to a NoiseProblem/EnsembleProblem. While the benefit of this framework is that it works in great generality, it is much slower and requires much more allocations than a more direct approach for problems that admit this. The following is 300x faster on my device and cuts allocations from 800.000ish to 18 in a simple example.

If such special-cases are desirable, what would be a good infrastructure (what I did now is just the first thing that came to mind); and would it be good to have a tracking issue to identify (and solve) such special cases?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions