Shrink down 2D and 3D general reduction tests to control time and space.
(1) Apply Z-dimension limiting to 3D correctness tests.
The Z dimension is always handled specially by GPU drivers, and a high
value for this dimension can have serious performance implications.
For example, Cuda and OpenCL encourage Z to be the smallest dimension.
We have observed that prior to this fix, this testing runs out of
memory when running as a 32-bit application on n6p.
(2) Increase sparseness of 2D and 3D correctness tests.
Before this change, reduction tests take about 7m on n6p as a 32-bit app.
After this change, reduction tests take about 3m on n6p as a 32-bit app.
Bug: 27299475
Change-Id: Id8241cc3e2d0abbd5f643d1266dc4317b91093a0
(cherry picked from commit 1430dcc4a9033ed874c89a014b3421884686c9d0)
1 file changed