> For the complete documentation index, see [llms.txt](https://docs.zama.org/tfhe-rs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/tfhe-rs/get-started/benchmarks/zk-proof-benchmarks.md).

# Zero-knowledge proof benchmarks

This document details the performance benchmarks of [zero-knowledge proofs](/tfhe-rs/fhe-computation/advanced-features/zk-pok.md) for [compact public key encryption](/tfhe-rs/fhe-computation/advanced-features/public-key.md) using **TFHE-rs**.

## Server-side computation

{% hint style="info" %}
Benchmarks were launched on an `AWS hpc7a.96xlarge` instance equipped with two 96-core `AMD EPYC 9R14 CPU @ 2.60GHz` and 740GB of RAM.
{% endhint %}

Proving and verification are done with tfhe-rs native executable on a powerful server.

### Fast proof / slow verify latency

![](/files/GUMbbszjKjpmSjBZQUtk)

### Fast proof / slow verify throughput

![](/files/dhMDYQoOakNZIgc1lVfw)

### Slow proof / fast verify latency

![](/files/KLUZfpoMsiRlgVHuTyKC)

### Slow proof / fast verify throughput

![](/files/oZC6dJrd8HU4zP5Vksyu)

## Client-side computation

{% hint style="info" %}
Benchmarks were launched on an `AWS m6i.4xlarge` instance equipped with a 16-core from a hypervisored `Intel Xeon Platinum 8375C CPU @ 2.90GHz` and 64GB of RAM.
{% endhint %}

Proving is done on a 16-core machine using WASM executable run on a Chrome browser to simulate a typical client configuration.

### Fast proof / slow verify latency

![](/files/oJncwEQG9HppjMuxv7yz)

### Slow proof / fast verify latency

![](/files/TBqi9AQK2Q7HZdKoMrpb)


---

# 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://docs.zama.org/tfhe-rs/get-started/benchmarks/zk-proof-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.