Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Optimize graph object buffering and flushing #395
Optimize graph object buffering and flushing #395
Changes from 1 commit
b9ef640
319f1d2
27949a9
6db9779
8d22caf
8196339
1271491
b05beb8
5c0ad98
b1c0804
43e57a9
2b1052c
47843b7
ca68b8a
06b3394
55bb7b5
2059ac5
a627688
6a2c2bf
b2b44c3
aba2ed6
cfbada4
e3d379a
cd586e1
d370104
3cb5160
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought: what information is typically gotten from previous entities? My first thought would be that it would usually only be foreign keys, which is likely just an id. Is it worth considering when we flush
InMemoryGraphObjectStore
, we maintain a map similar to the implementation ofDuplicateKeyTracker
. That way we could likely store much more than 500 entities and relationships for most of the use-cases of getEntity.Maybe we could get lucky and reduce roundtrips to the disk a good amount of the time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are definitely lots of additional caching improvements that we can make!
This file was deleted.