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

Multiquery optimization #376

Open
cbizon opened this issue Jun 3, 2022 · 0 comments
Open

Multiquery optimization #376

cbizon opened this issue Jun 3, 2022 · 0 comments

Comments

@cbizon
Copy link
Contributor

cbizon commented Jun 3, 2022

Right now, multiquery uses a shared cache, but that's not clearly a win because the cache is at the request/response level. That might work ok for the first hop, but rarely beyond that.

Another point worth considering:
Sometimes we will have a rule like (Pinned)-[related to]-(?)-[p1]-(?). and a different rule like (Pinned)-[associated with]-(?)-[p2]-(?). In this case, associated with is a subclass of related to, so running the associated with query in principle adds no new information and can be dispensed with.

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

No branches or pull requests

3 participants