Skip to content

Performance issues in history mechanism #90

@karger

Description

@karger

The history mechanism has been made central to exhibit. Interaction with a single component (such as changing the selection in a facet) now triggers a full "state update" which leads to every component being checked for changes. The change check can be expensive---proportional to the number of values in each facet. It would improve performance for the common case if full-state-update were only invoked during use of forward and back buttons.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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