---
title: "Discussion on \"Benchmark the whole verifier call, including its thread pool\" | Hashnode"
description: "Discussion on \"Benchmark the whole verifier call, including its thread pool\". Nine retained CPU observations show why timing boundaries and workload size matter when comparing verifier thread limits. Public data and code."
url: "https://hashnode.com/posts/benchmark-the-whole-verifier-call-including-its-thread-pool/6af7379df563cfd4a3950819"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Benchmark the whole verifier call, including its thread pool](https://nodus-compute.hashnode.dev/benchmark-the-whole-verifier-call-including-its-thread-pool?utm_source=hashnode&utm_medium=feed)

Nine retained CPU observations show why timing boundaries and workload size matter when comparing verifier thread limits. Public data and code.

4d ago · 4 min read · nodus-compute.hashnode.dev  
Read the article

-   [#python](https://hashnode.com/tag/python)
-   [#performance](https://hashnode.com/tag/performance)
-   [#concurrency](https://hashnode.com/tag/concurrency)

## Written by

[Viswaretas Kotra](https://hashnode.com/@viswa-kotra)

@viswa-kotra · San Francisco, USA

  
[View profile](https://hashnode.com/@viswa-kotra)

Founder @ Nodus Compute, previously in HFT, Distributed Systems, and AI.

Founder @ Nodus Compute

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
