-
Notifications
You must be signed in to change notification settings - Fork 144
GitHub actions regression test #499
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
Conversation
jvector-examples/src/main/java/io/github/jbellis/jvector/example/AutoBenchYAML.java
Show resolved
Hide resolved
|
I suggest editing the description of this PR with a high-level explanation of what it contains/does. It would be great if it also contained an example of the output. |
2792ac6 to
5ab589f
Compare
|
@tlwillke @marianotepper are we good to merge this or are there changes you would like to see? |
marianotepper
left a comment
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.
Looks ready to merge. We can continue improving this feature as we use it, but it is a solid starting point.
tlwillke
left a comment
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.
LGTM
| exit 0 | ||
| fi | ||
|
|
||
| # Determine available memory and set heap size to half of it |
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.
Double check that this setting will take priority over the Xmx set in the module's pom.xml (statically set to 14GB).
This PR introduces a new github workflow and associated code to perform automated regression testing across branches. The workflow can be triggered manually with the branches to compare included as inputs. It is also triggered to run automatically when a PR to main is opened, in which case it will run a regression test comparing the requested branch with main.
Metrics compared include QPR, average latency, and recall at k10. See attached for an example of the output.
benchmark_report.zip