emerge --sync takes a while to verify .tmp-unverified-downlo

[asaparov]

I've noticed emerge --sync on one of my machines takes a lot longer than the others, and almost all of the time is spent in Verifying /usr/portage/.tmp-unverified-download-quarantine.
It takes about a couple minutes to finish this step, whereas running

Code: Select all

gemato verify -K /usr/share/openpgp-keys/gentoo-release.asc /usr/portage

finishes in 26 seconds. Shouldn't emerge --sync only verify a small subset of the tree? If so, why would it be taking so much longer? My other machines go through this step fairly quickly.

emerge --info: https://pastebin.com/WaavzvzK

[mike155]

You could disable tree verification. That's what I do on my machines to speed up 'emerge --sync', especially on slow machines or on machines where /usr/portage is mounted via NFS.

• Emerge portage without USE flag 'rsync-verify' AND
• Add the lines below to the DEFAULT section of /etc/portage/repos.conf/gentoo.conf:

  Code: Select all

  sync-rsync-verify-metamanifest = no
  sync-allow-hardlinks = no

[eccerr0r]

Tree verification needs to verify the whole tree. I've found mechanical hard disks take much longer to sync because it needs to copy/link the whole tree to a different directory (depend on COW), sync in from remote repo, verify, and then sync to your normal portage tree.

So yes, it's quite a few cycles for your SSD too that you don't notice since it's quite fast.

Some people have enough RAM to copy the whole portage tree to ramdisk/tmpfs, wonder if this should be the better optimization, though hard links are fairly quick too (COW)...