[
https://issues.apache.org/jira/browse/ARROW-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16353051#comment-16353051
]
ASF GitHub Bot commented on ARROW-2071:
---------------------------------------
wesm commented on issue #1561: ARROW-2071: [Python] Fix test slowness on
Travis-CI
URL: https://github.com/apache/arrow/pull/1561#issuecomment-363249827
The pytorch conda packages are enormous. How important is it that we test
this on each CI build (versus in some kind of nightly integration test)?
```
The following packages will be downloaded:
package | build
---------------------------|-----------------
libgcc-5.2.0 | 0 1.1 MB defaults
pillow-5.0.0 | py27_0 958 KB conda-forge
libtiff-4.0.9 | 0 511 KB conda-forge
libtorch-0.1.12 | nomkl_0 1.7 MB defaults
olefile-0.44 | py27_0 50 KB conda-forge
torchvision-0.1.9 | py27hdb88a65_1 86 KB soumith
openblas-0.2.19 | 2 14.1 MB conda-forge
numpy-1.13.1 |py27_blas_openblas_200 8.4 MB
conda-forge
pytorch-0.2.0 |py27ha262b23_4cu75 312.2 MB soumith
mkl-2017.0.3 | 0 129.5 MB defaults
------------------------------------------------------------
Total: 468.6 MB
```
cc @cpcloud @robertnishihara @pcmoritz
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> [Python] Reduce runtime of builds in Travis CI
> ----------------------------------------------
>
> Key: ARROW-2071
> URL: https://issues.apache.org/jira/browse/ARROW-2071
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Wes McKinney
> Assignee: Antoine Pitrou
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> For some reason, recently each Python build has been taking about 15 minutes
> to run. I speculate this is due to VM thrashing caused by reduced resources
> on the Travis CI workers, related to the problem I fixed in ARROW-2062.
> We should experiment, but it seems like perhaps this can be fixed either by:
> * Reducing the size of the Plasma store on Travis CI
> * Disabling valgrind in Plasma tests
> The slowness could be caused by something else, though, so we should
> investigate (and have pytest report slow tests in the logs)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
