Skip to content

Conversation

@MarkWolters
Copy link
Contributor

@MarkWolters MarkWolters commented Dec 5, 2025

This PR adds new columns to the BenchYAML tests measuring memory and disk usage. The output looks as follows:

Configuration:
  efConstruction        : 100
  addHierarchy          : true
  neighborOverflow      : 1.2
  usePruning            : true
  M                     : 32

Overquery    Avg QPS (of 3)    ± Std Dev    CV %        Mean Latency (ms)    Avg Visited    Recall@10    Max heap usage    Max offheap usage    Total file size    Number of files    Index build time   
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1.00         45799.0           706.6        1.5         0.192                349.6          0.75         1127.6            116.5                116.5              1                  38.72              
2.00         38702.6           344.8        0.9         0.237                507.2          0.89         494.1             116.5                116.5              1                  38.72              
5.00         25087.6           463.2        1.8         0.363                922.1          0.95         795.4             116.5                116.5              1                  38.72              
10.00        16557.8           45.5         0.3         0.551                1512.0         0.97         1219.3            116.5                116.5              1                  38.72         

@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

Before you submit for review:

  • Does your PR follow guidelines from CONTRIBUTIONS.md?
  • Did you summarize what this PR does clearly and concisely?
  • Did you include performance data for changes which may be performance impacting?
  • Did you include useful docs for any user-facing changes or features?
  • Did you include useful javadocs for developer oriented changes, explaining new concepts or key changes?
  • Did you trigger and review regression testing results against the base branch via Run Bench Main?
  • Did you adhere to the code formatting guidelines (TBD)
  • Did you group your changes for easy review, providing meaningful descriptions for each commit?
  • Did you ensure that all files contain the correct copyright header?

If you did not complete any of these, then please explain below.

@MarkWolters MarkWolters marked this pull request as ready for review December 9, 2025 00:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants