Skip to content

Performance limitations of CompoundGenerator::get_point #69

Description

@c-mita

Malcolm has started running into problems where get_point is unable to keep up with the pace of scans (now into the kHz range) - buffering can only help so much.

get_point has quite a lot of indexing logic to retrieve the values from the component generators based on tiled masks. Can anything be done to simplify this, perhaps by pushing the memory-speed tradeoff made previously further in the "more memory for more speed" direction?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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