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

Performance: Consider in-memory store default #39

Open
jeswr opened this issue Mar 24, 2022 · 1 comment
Open

Performance: Consider in-memory store default #39

jeswr opened this issue Mar 24, 2022 · 1 comment

Comments

@jeswr
Copy link
Member

jeswr commented Mar 24, 2022

We are currently store implicit data in an n3 store however, the match method is quite heavyweight; especially in that it creates a full array of the matches before asynchronously iterating over them. As such it would likely be quite valuable to use something else that does not take such a performance hit.

@jeswr
Copy link
Member Author

jeswr commented Mar 26, 2022

Updates:

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

1 participant