Bug#980517: debsums: Parallel checking

[Witold Baryluk]

Package: debsums
Version: 3.0.1
Severity: minor
X-Debbugs-Cc: witold.baryluk at gmail.com

Hi.

On my 32 core system, and a lot of packages installed (~7000), it takes
about one hour for the debsum to check all the files. Despite ability to
read all files from the storage in about 4 minutes. The issue is use of
just one thread and most likely not optimized md5sum implementation.

I think it would be very useful to be able to specify number of parallel
threads to use when doing checking manually or from cron. I think it
would even be good to enable it by default. (for the case of use from
cron, usage of nice / schedtool and/or ionice could mitigate any issues
on server or laptops).

Regards,
Witold


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-1-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debsums depends on:
ii  libdpkg-perl          1.20.7.1
ii  libfile-fnmatch-perl  0.02-2+b8
ii  perl                  5.32.0-6
ii  ucf                   3.0043

debsums recommends no packages.

Versions of packages debsums suggests:
ii  bash-completion  1:2.11-2

-- no debconf information