You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to speed up the trufflehog git scan with this "--concurrency" arg. After some trials, it does not look very right.
As shown, it takes 14s when concurrency=1 while 15s when concurrency=8 (given my desktop has 8 cores), which contradicts with common sense. Could someone shed some light on this please? Thanks.
The text was updated successfully, but these errors were encountered:
I've also noticed strange behavior with the --concurrency switch. Even with the flag set to --concurrency=1, I can see more than one thread in the process list.
I've also noticed strange behavior with the --concurrency switch. Even with the flag set to --concurrency=1, I can see more than one thread in the process list.
I am also wondering about this.
I'm trying to use the --concurrency option to ensure that trufflehog sends data output to the Verification Server in an orderly fashion. For example, when scanning a folder with multiple files, I expected that setting --concurrency=1 would make trufflehog scan one file at a time and send the result sequentially to the Verification Server. However, it seems that even with --concurrency=1, the tool attempts to send data concurrently using multiple threads.
Could someone verify whether this behavior is expected or if it might be a bug? Thank you in advance to the developers.
I am trying to speed up the trufflehog git scan with this "--concurrency" arg. After some trials, it does not look very right.

As shown, it takes 14s when concurrency=1 while 15s when concurrency=8 (given my desktop has 8 cores), which contradicts with common sense. Could someone shed some light on this please? Thanks.
The text was updated successfully, but these errors were encountered: