Skip to content

potential performance regressions/opportunities in 6.x #48

Description

@ndwarshuis

This is a follow-up issue started from #46 (comment)

TLDR, I had to make some high-level abstractions to deal with complexity in order to fix some old bugs, and this slowed down some of the simpler parts of this API (querying planning/properties).

Solutions?

  • lazy eval (kinda easy)
  • tree-based diff algorithm (hard but would solve many more problems)

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