Twistcli scan takes longer with more images on local disk

[mzk5066]

Hi,
We have application which runs twistcli command line commands to scans images. If we delete an image after scan, and keep podman registry empty, the scan time in under 1min. But we made a change to not delete images after scan, so we can use the layers. With this change we are seeing twistcli scan time going up. It goes upto 5mins. Can you please us out here. Is there a requirement to keep less number of images locally for performance of twistcli scans.

Thanks and Regards,

[stumiki]

Hello,

Twistcli Scan depends on the size of the image/latency between the server/console, we scan at about 100mb per second, so most linux images are done in a few seconds, but as stated above sometimes network/image size configuration comes into play. Additional docs: https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/tools/twistcl...

[JJean-Claude]

Also, take into account the resource requirements for container and image scanning

https://docs.prismacloud.io/en/compute-edition/33/admin-guide/install/system-requirements

See the section called Defender Resource Requirements

Did a post help answer your question? Please click the “Accept as Solution” button. Read more about how and why accepting solutions is a vital part of LIVEcommunity.