Open cponder opened 3 years ago
Another variation is in the order of output between the single-GPU case
Running benchmark Spmv
result for spmv_csr_scalar_sp: 98.8228 Gflop/s
result for spmv_csr_scalar_sp_pcie: 3.1424 Gflop/s
result for spmv_csr_scalar_dp: 90.6637 Gflop/s
result for spmv_csr_scalar_dp_pcie: 2.0450 Gflop/s
result for spmv_csr_scalar_pad_sp: 88.7928 Gflop/s
result for spmv_csr_scalar_pad_sp_pcie: 3.3503 Gflop/s
result for spmv_csr_scalar_pad_dp: 81.4095 Gflop/s
result for spmv_csr_scalar_pad_dp_pcie: 2.8388 Gflop/s
result for spmv_csr_vector_sp: 135.6520 Gflop/s
result for spmv_csr_vector_sp_pcie: 3.1697 Gflop/s
result for spmv_csr_vector_dp: 118.4620 Gflop/s
result for spmv_csr_vector_dp_pcie: 2.0329 Gflop/s
result for spmv_csr_vector_pad_sp: 146.2390 Gflop/s
result for spmv_csr_vector_pad_sp_pcie: 3.3713 Gflop/s
result for spmv_csr_vector_pad_dp: 133.8620 Gflop/s
result for spmv_csr_vector_pad_dp_pcie: 2.8474 Gflop/s
result for spmv_ellpackr_sp: 117.4200 Gflop/s
result for spmv_ellpackr_dp: 93.4976 Gflop/s
and the multi-GPU case:
Running benchmark Spmv
result for spmv_csr_scalar_sp: 101.0680 Gflop/s
result for spmv_csr_vector_sp: 140.4280 Gflop/s
result for spmv_ellpackr_sp: 119.4360 Gflop/s
result for spmv_csr_scalar_dp: 91.7853 Gflop/s
result for spmv_csr_vector_dp: 121.0850 Gflop/s
result for spmv_ellpackr_dp: 94.9549 Gflop/s
I can see that the former splits the list by scalar/vector and the latter splits it by single/double. Maybe that's more intuitive for reading, but it also makes it harder to line up the results. I'd be inclined to order the latter as
Running benchmark Spmv
result for spmv_csr_scalar_sp: 101.0680 Gflop/s
result for spmv_csr_scalar_dp: 91.7853 Gflop/s
result for spmv_csr_vector_sp: 140.4280 Gflop/s
result for spmv_csr_vector_dp: 121.0850 Gflop/s
result for spmv_ellpackr_sp: 119.4360 Gflop/s
result for spmv_ellpackr_dp: 94.9549 Gflop/s
There are some minor differences in the format of the units that ought to be easy to fix:
where "GB/s" and "GB/sec" are both used, and similarly
I'd be inclined to use "sec" (and "msec") everywhere.