POC for Vespa search engine #1004
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds POC for Vespa search engine.
Creates a unified abstraction layer for clients + runners and adds vespa client + runners
Benchmarks can be run on Vespa with appropriate configurations + schema for deploying data. Example for nyc_taxis can be found on my fork here: https://github.com/OVI3D0/opensearch-benchmark-workloads/tree/multi-engine
To tell OSB we're running on vespa, we'll use a new
--database-typeargument. If not provided, OSB will assume we're running against an opensearch cluster. Otherwise, you can tell OSB to benchmark using vespa client + runners by adding--database-type=vespato your benchmark command.Issues Resolved
#1000
Testing
Still seems to be some issues with indexing due to 429 errors but I'm able to run a full benchmark E2E:
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.