if I am reading your timing document properly it looks like it has 66 files
that take ~20 seconds in total to run them all. I would consider that a
large number of super tiny tests, at which point the slower load time
really makes a difference. On the other hand if it took 20 seconds to run
them all, but there were only 4 files (5 seconds each to run) the startup
time would make little difference, and the faster run time would
potentially help out.

On Wed, May 11, 2016 at 7:16 PM, Tony Cook via RT wrote:
On Wed, May 11, 2016 at 06:38:59PM -0700, Chad Granum wrote:
The change ultimately results in a much faster runtime, but a slower
startup time. Test2 takes twice as long to load, but runs twice as fast
once loaded. The number of test files vs the length of the test files
usually explains why some suites are faster or slower.

I am not familiar with imager, does it have a large number of test files?
Imager has 66 test files, I'm not sure that counts as a large number.


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 7 of 11 | next ›
Discussion Overview
groupperl5-porters @
postedMay 11, '16 at 2:18a
activeMay 17, '16 at 5:24p



site design / logo © 2021 Grokbase