Repository navigation
Add reproducible Delicious GPU benchmarks with the paper evaluation protocol - #38
Draft
dev-rinchin wants to merge 9 commits into
Draft
dev-rinchin wants to merge 9 commits into
dev-rinchin wants to merge 9 commits into
Conversation
Define twelve deterministic workloads, including output scaling from 32 to 10000, multiple sketch strategies, validation memory and deep histograms. Measure synchronized wall time, private-pool peak live allocations, RSS and holdout quality in isolated workers. Store versioned raw evidence and reject incompatible result comparisons. Document a pinned environment and require local GPU reports in AGENTS.md.
Keep a fresh process per case and library version while avoiding duplicate import-time Numba compilation. Preserve intermediate timing evidence if the memory phase fails.
Record and display one-device execution, physical/CUDA-visible VRAM, GPU UUID, PCI bus, SM count, memory bus, power limit, maximum SM clock and driver versions. Show target dimension and sketch width per case, distinguishing projections from sampling with replacement. Add GPU-count and report regressions.
Avoid mismatched device identity when CUDA and nvidia-smi ordinal ordering differ. Reject selectors resolving to multiple cards or MIG instances.
Select suite manifests explicitly while preserving the original k=8 workload. Fingerprint the selected suite and verify that the k=5 variant changes only sketch width and benchmark identity.
Select the frozen k=5 profile by default in the loader and CLI, update repository instructions and documentation, and retain the explicit k=8 profile for historical comparisons.
dev-rinchin
marked this pull request as draft
November 2, 2026 08:51
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The default local GPU benchmark uses the real Delicious dataset and the evaluation protocol from the SketchBoost paper, replacing synthetic data in the required PR check.
Workload and reporting
Validation
d7be28b27614.da8df750a760and candidate4d2d89f67364. Both timing and separate memory fits passed; actual dataset checksums matched for all paired cases. Positive resume verification skipped completed cases. These diagnostic results are not a performance benchmark at convergence.Draft: the full five-fold comparison at the paper's 20000-iteration limit has not been run. The unsketched baseline is expensive: a separate 32-iteration pilot fit took approximately 114 seconds on an A100. Comparing two versions across all folds with separate full memory fits can take days. No full-protocol quality or performance result is claimed.