Brian Hulette commented on ARROW-2266:

The JS consumer is also to blame for the long runtime, since we validate each 
file with the entire matrix of build targets.  [~ptaylor]: Do you have any 
ideas to improve runtime? could we run all the targets in parallel?

> [CI] Improve runtime of integration tests in Travis CI
> ------------------------------------------------------
>                 Key: ARROW-2266
>                 URL: https://issues.apache.org/jira/browse/ARROW-2266
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Integration
>            Reporter: Wes McKinney
>            Priority: Major
> I was surprised to see that travis_script_integration.sh is taking over 25 
> minutes to run (https://travis-ci.org/apache/arrow/jobs/349493491). My only 
> real guess about what's going on is that JVM startup time on these hosts is 
> super slow.
> I can think of some things we could do to make things better:
> * Add debugging output so we can see what's slow
> * Write a Java integration test handler that validates multiple files at once
> * Generate a single set of binary files for each producer rather than 
> regenerating them each time (so Java would only need to produce binary files 
> once instead of 3 times like now)

This message was sent by Atlassian JIRA

Reply via email to