Comment # 13 on bug 1211554 from Bruno Friedmann

I mean most of the work was there to have this package.

I've quickly build and tested 1.2.1 and I agree there's a performance issue at
least with traditional clamscan, but there's also more virus known, and if I
add the functionality that tier can offer I would be more interested by
protecting myself from threads than counting performance.

clamscan -r --infected Documents/
----------- SCAN SUMMARY -----------
Known viruses: 8677705
Engine version: 1.2.1
Scanned directories: 113
Scanned files: 1380
Infected files: 0
Data scanned: 5498.37 MB
Data read: 3326.20 MB (ratio 1.65:1)
Time: 1056.323 sec (17 m 36 s)
Start Date: 2023:11:06 17:01:45
End Date:   2023:11:06 17:19:21


clamscan -r --infected Documents/
----------- SCAN SUMMARY -----------
Known viruses: 8677603
Engine version: 0.103.11
Scanned directories: 113
Scanned files: 1380
Infected files: 0
Data scanned: 3728.95 MB
Data read: 3326.20 MB (ratio 1.12:1)
Time: 505.956 sec (8 m 25 s)
Start Date: 2023:11:06 16:43:00
End Date:   2023:11:06 16:51:26

What is really strange is the amount of Data Scaned (almost twice in 1.2.1)

But of course this is my humble needs on restricted number of platform (TW
64bits).

Hope this can be sorted out soon.