-
Notifications
You must be signed in to change notification settings - Fork 157
fix for disk usage measurements #692
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
Open
MarkWolters
wants to merge
4
commits into
main
Choose a base branch
from
track_disk_correctly
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1f58473
fix for disk usage measurements
MarkWolters 334ebb8
adding release notes
MarkWolters 08967cd
moved BuildOnDiskResult to above BuildOnDisk method and fixed incorre…
MarkWolters ae57e7b
Restored accidentally deleted javadoc for ConstructionMetrics
MarkWolters File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| ## This PR is a fix for an issue in how file sizes were calculated by the JVector test harness, i.e. BenchYAML and AutoBenchYAML. | ||
|
|
||
| ## Problem 1: The index cache directory accumulates across runs | ||
|
|
||
| In Grid.runOneGraph (and runAllAndCollectResults), BenchmarkDiagnostics monitors two directories: | ||
| diagnostics.startMonitoring("testDirectory", workDirectory); | ||
| diagnostics.startMonitoring("indexCache", Paths.get(indexCacheDir)); // "index_cache/" | ||
| getTotalBytes() sums both. The index_cache/ directory is persistent — it is never wiped between runs. So the reported disk figure grows monotonically across the run, regardless of which configuration is under test. The delta | ||
| between a fused-PQ run and a non-fused-PQ run is invisible. | ||
|
|
||
| ## Problem 2: Even within a single run, the snapshot captures all feature sets, not just one | ||
|
|
||
| When multiple feature sets are built in the same runOneGraph call, the directory total covers all of them. You can't attribute disk usage to a specific configuration from that number. | ||
|
|
||
| There is even a TODO in the code acknowledging this at line 233: | ||
| // TODO this does not capture disk usage for cached indexes. Need to update | ||
|
|
||
|
|
||
| --- | ||
| ## The fix | ||
|
|
||
| Rather than directory-level monitoring, measure the specific graph file for each feature set directly after it is written. In buildOnDisk, the path for each feature set's graph file is already computed: | ||
|
|
||
| if (handles.containsKey(features)) { | ||
| graphPath = handles.get(features).writePath(); | ||
| } else { | ||
| graphPath = outputDir.resolve("graph" + n++); | ||
| } | ||
|
|
||
| After the build completes, Files.size(graphPath) gives the exact on-disk size for that specific configuration. This value should be returned from buildOnDisk (as part of a result map keyed by feature set) and then included | ||
| in the BenchResult params or metrics map alongside the other per-configuration numbers. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.