- 新しい順
- 投票が多い順
- コメントが多い順
Hi,
is it possible to reach us via a ticket (TT). That way we have access to your instance and we can investigate deeper. For example it would be interesting to know what would be the size of the result approximately.
As an alternative for now I wonder if you can split the query in multiple steps, each of them retrieving a subset of the data.
Gremlin also has support for query profiling but this is only useful when query completes: https://docs.aws.amazon.com/neptune/latest/userguide/gremlin-profile-api.html
--Gabriel
Adding limit(1) fixed it, not sure how though.
g.V().hasLabel('MyVertex').has('myLabel',1234).outE().hasLabel('MY_EDGE_LABEL').count().limit(1).next()
Hi BaluVV,
Neptune engine for Gremlin processes solutions in chunks and specifying a limit(1) has the behavior of hinting the engine to process one solution at a time at each query step (node) instead of processing a chunk at a time. Setting a lower chunk size has a proportional effect on latency. You can observe the same indicated using "chunkSize" attribute in the query profile or explain output. If you need more assistance, please reach out through a support ticket.
Thanks.
関連するコンテンツ
- AWS公式更新しました 4年前
- AWS公式更新しました 2年前
- AWS公式更新しました 4年前