> For the complete documentation index, see [llms.txt](https://summa.gitbook.io/summa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://summa.gitbook.io/summa/1/backend/summa-solvency/benchmarks.md).

# Benchmarks

Benchmarks ran on an AWS m7a.8xlarge with 32 cores and 128GB RAM. The generics parameters are : 

* `N_CURRENCIES = 1` 
* `N_BYTES = 8`
* `LEVELS=20` (2^20 users = 1,048,576 users)

**Merkle Sum Tree**

| MST init |
| -------- |
| 24.542 s |

| MST init (sorted) |
| ----------------- |
| 25.754 s          |

**Proof of Inclusion Circuit**

<table><thead><tr><th>VK Gen</th><th width="110">Pk Gen</th><th width="161">Proof Generation</th><th width="175">Proof Verification</th><th>Proof Size (bytes)</th></tr></thead><tbody><tr><td>106.88 ms</td><td>125.87 ms</td><td>403.33 ms</td><td>4.0000 ms</td><td>1632</td></tr></tbody></table>

To reproduce benchmarks like the one above, please refer to [this](https://github.com/summa-dev/summa-solvency/blob/master/zk_prover/benches/full_solvency_flow.rs)

The benchmark results based on larger userbase (2^28) are in the table below:

| MST init |
| -------- |
| 6279.0 s |

<table><thead><tr><th>VK Gen</th><th width="110">Pk Gen</th><th width="161">Proof Generation</th><th width="175">Proof Verification</th><th>Proof Size (bytes)</th></tr></thead><tbody><tr><td>110.61 ms</td><td>152.24 ms</td><td>460.05 ms</td><td>4.0001 ms</td><td>1632</td></tr></tbody></table>

Notably, the results show that there is no significant time difference in the Proof generation or verification between the two datasets despite the substantial increase in entry size.

Custodians can reduce the time required to build a Merkle sum tree by utilizing [`summa-aggregation`](/summa/1/backend/summa-aggregation.md). For detailed benchmark results, please refer to [here](/summa/1/backend/summa-aggregation/benchmarks.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://summa.gitbook.io/summa/1/backend/summa-solvency/benchmarks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.