Publish Repo takes just as long as empty publish update

[reverson]

On Aptly 1.6.0, when initially publishing, or updating a published repo (even with 0 changes), the publish step takes a very long time, even with relatively few packages (compared to others).

We have our main Aptly data store on a gp3 EBS volume, and are publishing to S3. We are running within a kubernetes cronjob, but the publish takes that long even if I run it multiple times within the same pod.

This is in our dev environment, which just has a few test packages, our prod environment has many more packages, and takes at least 3x as long.

In previous issues it was recommended to use strace to see what was happening, but I'm just seeing a lot of reads and writes, each time, so it appears it isn't stuck on anything in particular.

time aptly publish repo --skip-contents --batch --architectures="amd64,arm64,all" --gpg-key="$KEYID" --passphrase-file=/tmp/$REPO_NAME-gpg-passphrase.txt $REPO_NAME "$PUBLISH_TARGET"
Loading packages...
Generating metadata files and linking package files...
Finalizing metadata files...
Signing file 'Release' with gpg, please enter your passphrase when prompted:
Clearsigning file 'Release' with gpg, please enter your passphrase when prompted:

Local repo jammy has been successfully published.
Now you can add following line to apt sources:
  deb http://your-server/ jammy main
Don't forget to add your GPG key to apt with apt-key.

You can also use `aptly serve` to publish your repositories over HTTP quickly.

real	35m58.211s
user	1m3.757s
sys	2m29.178s


time aptly publish update --batch --gpg-key="$KEYID" --passphrase-file=/tmp/$REPO_NAME-gpg-passphrase.txt $REPO_NAME "$PUBLISH_TARGET"
Loading packages...
Generating metadata files and linking package files...
Finalizing metadata files...
Signing file 'Release' with gpg, please enter your passphrase when prompted:
Clearsigning file 'Release' with gpg, please enter your passphrase when prompted:
Cleaning up published repository s3:BUCKET_NAME:./jammy...
Cleaning up component 'main'...

Published local repository s3:BUCKET_NAME:./jammy [all, amd64, arm64] publishes {main: [jammy]} has been updated successfully.

real	36m47.555s
user	1m3.275s
sys	2m22.603s

[reverson]

I just tested this with 1.6.1 and am seeing the same behavior.