Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSpeed up test suite #412
Speed up test suite #412
Comments
|
The doctests take longer than the nofib tests on my machine. I think that is because it has to recompile all modules before it can run the doctests. |
|
Blackscholes is the test that takes the longest on my machine (about 2 seconds). It doesn't seem like it would benefit from using Otherwise maybe the generation of the array can be sped up. Now, it first generates a list and then converts that to an array (maybe some of this is fused away?). |
|
Generating large test arrays is important for the parallel backends, because they can use different implementations for larger arrays (for example the GPU backends need to use multiple thread blocks after a certain (hardware dependent) size). It definitely could be a problem with the random number/array generation, we should look into that as well. |
The standard accelerate test suite, used by all the backends, can be quite slow. Several of the tests are significantly slower than the others, for example segmented folds and scans, which I believe is because the reference implementations are very inefficient. Writing some more efficient reference implementations (e.g. using
Data.Vector.Unboxed) should help speed things up.