Repository navigation
Trim redundant benchmark sweep points #871
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
base: dev
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -37,12 +37,13 @@ auto constexpr SKEW = 0.5; | |||||
| auto constexpr BATCH_SIZE = 1'000'000; | ||||||
| auto constexpr INITIAL_SIZE = 50'000'000; | ||||||
|
|
||||||
| auto const N_RANGE = nvbench::range(10'000'000, 100'000'000, 20'000'000); | ||||||
| auto const N_RANGE_CACHE = | ||||||
| std::vector<nvbench::int64_t>{8'000, 80'000, 800'000, 8'000'000, 80'000'000}; | ||||||
| auto const OCCUPANCY_RANGE = nvbench::range(0.1, 0.9, 0.1); | ||||||
| auto const MULTIPLICITY_RANGE = std::vector<nvbench::int64_t>{1, 2, 4, 8, 16}; | ||||||
| auto const MATCHING_RATE_RANGE = nvbench::range(0.1, 1., 0.1); | ||||||
| auto const SKEW_RANGE = nvbench::range(0.1, 1., 0.1); | ||||||
| // Sweeps keep the end points and the points where the curves bend. Denser sweeps can be run | ||||||
| // on demand with an nvbench axis override, e.g. `-a "Occupancy=[0.1:0.9:0.1]"`. | ||||||
| auto const N_RANGE = std::vector<nvbench::int64_t>{10'000'000, 50'000'000, 90'000'000}; | ||||||
| auto const N_RANGE_CACHE = std::vector<nvbench::int64_t>{8'000, 800'000, 8'000'000, 80'000'000}; | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Small table sizes are purely launch overhead. Added two more data points where the drop should be visible. |
||||||
| auto const OCCUPANCY_RANGE = std::vector<nvbench::float64_t>{0.1, 0.5, 0.8, 0.9}; | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
0.1 is irrelevant. |
||||||
| auto const MULTIPLICITY_RANGE = std::vector<nvbench::int64_t>{1, 4, 16}; | ||||||
| auto const MATCHING_RATE_RANGE = std::vector<nvbench::float64_t>{0.1, 0.5, 1.}; | ||||||
| auto const SKEW_RANGE = std::vector<nvbench::float64_t>{0.1, 0.3, 1.}; | ||||||
|
|
||||||
| } // namespace cuco::benchmark::defaults | ||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -15,7 +15,6 @@ using BF_KEY = nvbench::int64_t; | |||||
|
|
||||||
| static constexpr auto BF_N = 1'000'000'000; | ||||||
|
|
||||||
| auto const BF_SIZE_MB_RANGE_CACHE = | ||||||
| std::vector<nvbench::int64_t>{1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048}; | ||||||
| auto const BF_SIZE_MB_RANGE_CACHE = std::vector<nvbench::int64_t>{1, 4, 16, 64, 256, 1024}; | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Sizes below 16MB are basically noise or launch overhead. I would add back 32 and 128MB as this is the interesting region where throughput drops from L2 to DRAM. |
||||||
|
|
||||||
| } // namespace cuco::benchmark::defaults | ||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -151,14 +151,14 @@ NVBENCH_BENCH_TYPES(hyperloglog_e2e, | |||||
| NVBENCH_TYPE_AXES(TYPE_RANGE, nvbench::type_list<distribution::uniform>)) | ||||||
| .set_name("hyperloglog_e2e_uniform") | ||||||
| .set_type_axes_names({"T", "Distribution"}) | ||||||
| .add_int64_power_of_two_axis("NumInputs", {28, 29, 30}) | ||||||
| .add_int64_axis("SketchSizeKB", {8, 16, 32, 64, 128, 256}) // 256KB uses gmem fallback kernel | ||||||
| .add_int64_power_of_two_axis("NumInputs", {28}) | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
More stable results. |
||||||
| .add_int64_axis("SketchSizeKB", {32, 64, 128, 256}) // 256KB uses gmem fallback kernel | ||||||
| .add_int64_axis("Multiplicity", {1}); | ||||||
|
|
||||||
| NVBENCH_BENCH_TYPES(hyperloglog_add, | ||||||
| NVBENCH_TYPE_AXES(TYPE_RANGE, nvbench::type_list<distribution::uniform>)) | ||||||
| .set_name("hyperloglog_add_uniform") | ||||||
| .set_type_axes_names({"T", "Distribution"}) | ||||||
| .add_int64_power_of_two_axis("NumInputs", {28, 29, 30}) | ||||||
| .add_int64_axis("SketchSizeKB", {8, 16, 32, 64, 128, 256}) | ||||||
| .add_int64_power_of_two_axis("NumInputs", {28}) | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
More stable results
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. dang this is 8GB in keys. I guess 4Gb is fine too |
||||||
| .add_int64_axis("SketchSizeKB", {32, 64, 128, 256}) | ||||||
| .add_int64_axis("Multiplicity", {1}); | ||||||
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.
Optional. I think having at least 4 data points on the major axis gives better interpretability. 90M lands on a weird spot where
dynamic_mapallocates a third submap with only a few entries in it.