<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 7, 2017 at 9:12 AM, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, May 6, 2017 at 7:01 PM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a>> wrote:<br>
><br>
> Obviously, if I'm syncing a single repo, why is it fetching metadata from<br>
> other repos?<br>
> We perhaps need to start splitting the config files to multiple conf files?<br>
> It makes sense anyway, especially if we run the reposync per each repo<br>
> independently anyway?<br>
<br>
<br>
</span>Yep, unfortunately reposync reads all repos in the config, despite the<br>
fact only one is enabled for each run. Though I hope that we only pay<br>
the penalty for the first repo, so that the next repos should already<br>
use the metadata fetched during the first repo synchronization. Thus<br>
the overall running time difference should be small. If it fetches the<br>
metadata for all repos over and over again then it is a problem.<br></blockquote><div><br></div><div>It indeed looks like it's only happening for the 1st run.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Splitting the repo file makes sense, but it might make it harder to<br>
maintain, and as I said, I'm not sure if it will have significant<br>
effect on the running time.<br></blockquote><div><br></div><div>It might be actually easier, if different suites can share some repo configurations. Not sure.</div><div>Y.</div><div> </div></div><br></div></div>