admin管理员组

文章数量:1289866

I use AWS Opensearch Serverless index in my system. I have around 1M documents with parent child relationship. I do aggregation in the data. I have exposed API with the Opensearch at the backend.

When i hit the API, in backend i construct opensearch aggs query and use _search API to hit opensearch and return the response to the client. The issue is when i try the API in postman i get milliseconds response. But when i hit around 10 - 15 parallel API calls from the UI / Client side. I get an delay of around 6-7 seconds.

Just wanted to figure out why is it happening like this.

I use AWS Opensearch Serverless index in my system. I have around 1M documents with parent child relationship. I do aggregation in the data. I have exposed API with the Opensearch at the backend.

When i hit the API, in backend i construct opensearch aggs query and use _search API to hit opensearch and return the response to the client. The issue is when i try the API in postman i get milliseconds response. But when i hit around 10 - 15 parallel API calls from the UI / Client side. I get an delay of around 6-7 seconds.

Just wanted to figure out why is it happening like this.

  • amazon-web-services
  • amazon-opensearch
Share Improve this question edited Feb 20 at 17:09 Ken White 126k15 gold badges236 silver badges464 bronze badges asked Feb 20 at 17:07 Gowtham S SGowtham S S 12 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

You might want to setup cloudwatch logs to see if there is any API throttling from the Opensearch cluster. In my experience when I call many API's concurrently AWS tends to limit them.

本文标签： amazon web servicesParallel search request hits gives delayed responseStack Overflow

版权声明：本文标题：amazon web services - Parallel search request hits gives delayed response - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1741418564a2377667.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。