Splitting cuda dev files to use smaller sizes for cpu validation compared to profiling

[ChrisDryden]

Trying to come up with some examples of beginner friendly issues that would be helpful to the development effort:

Currently when profiling the CUDA kernels the first step is to validate that the output of the CPU implementation matches the CUDA implementation but for larger values the CPU implementation is extremely slow, would be good to split the performance measuring sizes and the correctness sizing so that the iteration speed for testing changes is significantly faster.

I think it would also be beneficial to have the code that measures the speed vs various block sizes as an option with the one that's used in the final model indicated in the code so that when profiling its easier to use and by default compare it only to the one thats used in the final model with the option to test all as a parameter.