On Tue, Apr 19, 2016 at 12:21 AM, Srinidhi B wrote:

Hello Dinar,

...

...

...

On Tuesday, 19 April, 2016 at 03:37 AM, Dinar Valeev wrote: Hi,

I'm looking for a solution to fix a slow ftp tree build, it takes about 5 hours to build it. It is fine to wait, but in Tumbleweed days where many snapshots released during the week this is rather slow.

First of all, I'm not an expert and this might not be a "solution", but a few months back I enabled "caching" on our KIWI worker and build times have significantly improved.

# grep CACHE /etc/sysconfig/obs-worker OBS_CACHE_DIR="/path/to/pkg-cache" OBS_CACHE_SIZE="50000" OBS_WORKER_CACHE_SIZE="" We need to have a cache big enough to fit all ports in.

I've looked at build36, it doesn't use cache at all. I reconfigured it, let see what would be an improvement if any. Thanks,

I'm not sure if there are any disadvantages of using caching, but purely from "build time" perspective, we have seen a lot of improvement!

Hope this helps, Srinidhi.

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Dinar Valeev writes:

So far cache is growing but it is now 78G and keeps growing?

That's about you need for a single biarch repo.

I wonder how much space we need per FTP tree?

50G at minimum. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Hello Dinar,

...

...

On Tuesday, 19 April, 2016 at 05:43 PM, Dinar Valeev wrote: That's about you need for a single biarch repo. It is 130GB now. So my native worker wouldn't fit here. It have only 96GB of RAM

Might be a stupid question, but the cache is on physical disk and bs_worker will use this cache in a VM running in RAM. Correct? So you could actually store 150GB+ cache but may not use the exact size when building the product. I have no experience in building such huge product ISOs, so I could be wrong. We build a relatively small (~800MB) add-on product ISO, but our package cache is already 49GB - almost all of the size allocated to the cache! :) Srinidhi. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org