Does this do concurrent access?

Due to a golang toolchain regression, one previously was able to observe failure to decrypt secrets - but only when accessed concurrently.

Does this benchmark tool use multi-threading to concurrently unseal same or different secrets, or can be configured to do so?

Start by reviewing the benchmark tool's entry points and configuration to determine whether it unseals the same or different secrets concurrently. Compare its behavior with the reported concurrent decryption failure and identify what evidence would establish support for configurable concurrency. Done means the concurrency behavior is documented or the requested configuration scope is clearly defined.

Written by the indexing model from the issue text.