Entity fetching optimization #559
Comments
novoj
added a commit
that referenced
this issue
May 10, 2024
When the entity is fetched from the data store, it's entity body storage part is always fetched twice. This becomes a problem when a large number of entities are fetched from the data store, and when the OS file cache is cold, it can mean twice the latency. This fetching is not entirely necessary if we refactor the `enrichEntity` method into two separate ones and call the second one only conditionally.
novoj
added a commit
that referenced
this issue
May 10, 2024
perf(#559): Entity fetching optimization
novoj
added a commit
that referenced
this issue
May 11, 2024
Fixes revealed by documentation tests. Entities used wrong predicates when prefetched.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the entity is fetched from the data store, it's entity body storage part is always fetched twice. This becomes a problem when a large number of entities are fetched from the data store, and when the OS file cache is cold, it can mean twice the latency. This fetching is not entirely necessary if we refactor the
enrichEntitymethod into two separate ones and call the second one only conditionally.The text was updated successfully, but these errors were encountered: