[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23806#comment-23806
 ] 

eyal edri [Administrator] commented on OVIRT-902:
-------------------------------------------------

I think we see the slowness also on experimental flows, same actions which 
takes a few seconds w/o mock takes 2 min when running with mock runner.
So we should probably give priority to checking the caching options.

> Speed up mock_runner.sh setup time by using caches.
> ---------------------------------------------------
>
>                 Key: OVIRT-902
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: Barak Korren
>            Assignee: infra
>            Priority: High
>              Labels: mock, mock_runner.sh, standard-ci
>
> We've already known that setting up mock takes a while, but mock has some 
> built-in caching features that should allow us to speed this up.
> We need to ensure those features are enabled by mock_runner.sh. The mock 
> options to look at are:
> * root_cache_enable
> * yum_cache_enable
> Both these options should be set to true in the mock chroot config file.
> We've been using these option downstream in minimead and the vdsm build 
> scripts, so they should be safe to use.



--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Reply via email to