You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2019/10/30 00:06:00 UTC

[jira] [Commented] (BEAM-8380) Use persistent caching with pip

    [ https://issues.apache.org/jira/browse/BEAM-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962550#comment-16962550 ] 

Kyle Weaver commented on BEAM-8380:
-----------------------------------

Pip caching may be useful, but for the particular case of the containers build, most of the time is spent pulling golang dependencies.

> Use persistent caching with pip
> -------------------------------
>
>                 Key: BEAM-8380
>                 URL: https://issues.apache.org/jira/browse/BEAM-8380
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Ahmet Altay
>            Assignee: Kyle Weaver
>            Priority: Major
>
> Use a persistent cache directory for pip install calls (at https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L1771 and some more in that file.)
> Pip does support caching (https://pip.pypa.io/en/stable/reference/pip_install/#caching) but the default directory may not be persistent across jobs.
> [~ibzib] you mentioned that this might help with container build times. Containers are build by runnin pip inside the container, I am not sure if that will be possible to use the same shared cache for that process or not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)