Hi Richard, thank you for following up.
Quoting Richard Lewis (2024-11-18 09:55:08) > > Wow, this is wild. Your directory schroot with overlayfs is about half a > > minute faster. Would you mind helping me getting more to the bottom of > > this? > > > > My system is an ARM Cortex A73 with 3.6 GB of RAM. To give you an idea > > about how slow that system is: its CPU Mark score is about half of my 11 > > year old Intel Core i5 Thinkpad. It takes 20 seconds before a video on > > youtube starts playing. On that system, a buildd chroot tarball extracts > > in under 2 seconds. So unless your own system is massively slower than > > mine (raspberry pi 1 would come to mind), the fact that unshare uses a > > tarball and you are using a directory schroot, does not explain the > > difference of 30 seconds. > > > i think quite a bit (but not all - running unzstf takes ~5-8 secs, is > unpacking the .tar.zstd ) is extracting the tarball vs being a directory. i > tried with just a .tar and it saved about 5 seconds (about 1-2s unpacking). But 5-8 second unpack time do not explain the 30 second difference. Are there more packages than the variant buildd installed in your schroot directory? Can you compare build logs between your schroot build and the unshare build to figure out where the extra time is spent? Maybe run sbuild --verbose under annotate-output? > it's a vps so limited ram (1GB i think), a swap file and not proper hardware > -- I dont know the details (and i dont think you can buy it this low-powered > any more), > > nproc says 1 so that might be part of the issue? (i know nothing about > hardware -- let me know if there are other commands that help). > > (a laptop would be faster, but not available everywhere!) 1 GB RAM and only single core is fine. I don't want to make sbuild less usuable on setups like yours and the limitations of my own system serve as a motivation for that. Thanks! cheers, josch
signature.asc
Description: signature
