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?
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?