I noticed that this particular unit test takes a relatively long time to run. Is it OK to shorten it?
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
If we're asking the question - why does this need to be 1024? What's the
specific purpose of the iteration? (why would 1 be too few iterations, for
example?)
Comment Actions
Address some of @dblaikie's concerns:
- Only test doCompression = true.
- Move away from a statistical approach.
Comment Actions
please do not remove the no compression path. I think we should just keep your original change of making the iteration to a smaller number. With the latest change plus 1024 iteration, the test time is ~20ms. I am ok with shorten the iteration further if we think 20ms is too costly.