Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Performance issues in history mechanism #90

Open
karger opened this issue Oct 7, 2012 · 0 comments
Open

Performance issues in history mechanism #90

karger opened this issue Oct 7, 2012 · 0 comments
Labels
Feature Priority:Low

Comments

@karger
Copy link
Contributor

karger commented Oct 7, 2012

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Priority:Low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karger