You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make an informed decision about the offset type solution, we would like to have a complete understanding of the impact on each CUB algorithm. Therefore, for each algorithm, we'd like a table that summarizes the following:
Performance with i32, u32, i64, u64 offset type
Verify that the algorithm still passes unit tests with this offset type
Report box plot of performance impacts across range of data types, input sizes, etc.
Can be summarized in table as min/max/median
The content you are editing has changed. Please copy your edits and refresh the page.
In order to make an informed decision about the offset type solution, we would like to have a complete understanding of the impact on each CUB algorithm. Therefore, for each algorithm, we'd like a table that summarizes the following:
Algorithms
System & environment
Benchmark data
device_exclusive_scan_max
Results
device_exclusive_scan_sum
Results
device_exclusive_scan_by_key
Results
device_select_flagged
Results
device_select_if
Results
device_partition_if
Results
device_partition_flagged
Results
device_run_length_encode
Results
device_run_length_encode_non_trivial_runs
Results
The text was updated successfully, but these errors were encountered: