imbajin commented on PR #3140:
URL: https://github.com/apache/hugegraph/pull/3140#issuecomment-5262149789
A few follow-up performance directions to keep in mind after this PR lands:
1. Partition pruning / fan-out reduction
- Avoid opening streams for partitions that cannot match the range.
- This is usually the highest ROI improvement because it cuts RPCs and
merge width directly.
2. Adaptive page size
- Replace the fixed 64-entry page with a size chosen by `limit`,
partition count, and observed latency.
- Good first optimization candidate because it is mostly a policy change,
not a protocol change.
3. Prefetch / pipeline
- Start fetching the next page before the current page is fully consumed.
- Useful for latency, but needs careful cancellation and cleanup handling.
4. Deeper merge pushdown
- Let Store side merge more aggressively so the client merges fewer
streams.
- Highest structural cost, because it tends to touch cursor semantics,
paging state, and protocol/versioning.
My suggestion is to keep this PR focused on correctness and use the items
above as a follow-up sequence, roughly in the order listed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
