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.

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

Improve status API performance #100

Closed
jbornemann opened this issue Jan 14, 2016 · 1 comment
Closed

Improve status API performance #100

jbornemann opened this issue Jan 14, 2016 · 1 comment
Assignees

Comments

@jbornemann
Copy link
Member

jbornemann commented Jan 14, 2016

Grabbit is computing status by fetching, and iterating through structures in an n+1 problem sort of manner. O(n^2) from quick observation. No caching/memoization.

As a good first step, we need :

1.) var/grabbit JCR indexing, but keeping in mind that we don't want indexing of volitile, active write persistence - as this will cause reindexing churn.
2.) Favor JCR queries over programmatic resource iteration

@jbornemann
Copy link
Member Author

@jdigger @sagarsane per our discussions. Feel free to add more detail

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

No branches or pull requests

2 participants