Thread Pool Management
Verity’s Prover includes a mechanism to optimise proving times.
The Verity Prover includes a mechanism to initialise warm MPC connection threads by server domain.
This feature significantly improves time to response (TTR) and time to proof (TTP).
By default, each request to the /proxy
endpoint triggers the setup of a new MPC connection thread in a cold start manner. This process takes 2–3 seconds per request, depending on the geographic distance between the Prover and the source server.
With thread management, the Prover can pre-prepare these connections for expected requests to the source server domain. This enables a warm start, cutting the response time for verifiable requests by 2–3 seconds.
Note: TTR increases proportionally with the size of the request/response:
- For data transfers < 3 KB, TTR is 1–5 seconds.
- For data transfers ~25 KB, TTR increases to around 20 seconds.
Managing Thread Pools
Pool management via /pools
API endpoint
To get statistics of all the pools
To get statistics of pool for a specific domain
To create a pool for a domain
To drop an existing pool
Creating a pool via /prepare
API endpoint and T-PREPARE
header
Creating a pool via /proxy
API endpoint and T-PREPARE
header
This works only for the very first proxy request, when there is no pool for the domain. If the pool already exists, the T-PREPARE
header is ignored.