Repository navigation
[Suggestion] Use multi-thread when running "aptly publish" without "-skip-contents" #1544
Description
Hi!
It's been a great adventure for a newbie like me using aptly to create my first local apt repo!
But me myself, and many others have encountered the problem, that "aptly publish" without "-skip-contents" is very slow, like here and there.
I found that, there's a progress running on single-thread, not using any other CPU core.
At the same time, iotop shows that the hard disk IO isn't too much. So I guess the bottle neck is CPU single-thread.
Google says the "Contents-.gz" is needed when using apt-file, but it's okay for regular apt operations if this file is missing.
So... Could it be possible to use multi-thread, or use something like gnu parallel, when running xz?
Activity
r4co0n commentedon Jul 10, 2026
If I am not mistaken, the
xzthread you see here is unpacking a deb-package, to extract the filecontrolfrom thecontrol.tar.xzsubarchive. These files need to be gathered to generateContents, if we skip generating the file via-skip-contents, extraction ofcontrolis no longer necessary.aptlyshould be able to extractcontrolfrom many packages at the same time, as you suggest, I suppose. Please note that sometimes the archives are packed usinggziporzstd, but this should not be a hurdle for this suggestion.