-
Notifications
You must be signed in to change notification settings - Fork 144
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
Update performance test with nested field #1488
Conversation
343cc30
to
becceb5
Compare
@heemin32 Please add the details around Cluster and client configuration used to run the benchmarks. |
Updated |
1cbd327
to
e6a8a06
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1488 +/- ##
=========================================
Coverage 85.02% 85.02%
+ Complexity 1278 1277 -1
=========================================
Files 167 167
Lines 5207 5207
Branches 493 493
=========================================
Hits 4427 4427
+ Misses 573 572 -1
- Partials 207 208 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Heemin Kim <heemin@amazon.com>
This PR contains only changes in benchmark/perf-test. Build failure has nothing to do with this change. |
@@ -9,7 +9,7 @@ steps: | |||
index_name: target_index | |||
- name: create_index | |||
index_name: target_index | |||
index_spec: release-configs/faiss-hnsw/nested/simple/index.json | |||
index_spec: release-configs/lucene-hnsw/nested/simple/index.json |
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.
why we're changing faiss
to lucene
here?
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.
It was a bug introduced before. This is test spec for lucene.
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-1488-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 fe774f751b5eeeea8a0163dfcf7a905e2eb7db81
# Push it to GitHub
git push --set-upstream origin backport/backport-1488-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
Description
Because the number of items inside nested field is too big(1000, 10001), if it is included in
source
, the query latency becomes around 1s. To have fair comparison with other test case, excluding nested field from being stored insource
.Configurations
Data Sets
Total Queries: 10,000
Cluster Configuration
Client Configuration
Faiss (1000 to 10000 items in nested field)
Lucene(1000 to 10000 items in nested field per doc)
Faiss(10 items in nested field per doc)
Lucene(10 items in nested field per doc)
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.