> 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/configuration/system-tuning.md).

# System tuning

This document lists OS-level settings that have a measurable impact on **TFHE-rs** performance. They are independent of the Rust toolchain and feature configuration described in [Advanced Rust setup](/tfhe-rs/configuration/rust-configuration.md).

## Huge pages on Linux

**TFHE-rs** server keys and intermediate buffers are large (typically hundreds of MB to several GB depending on parameters).

On Linux, backing these allocations with huge pages reduces TLB pressure and noticeably improves throughput on PBS-heavy workloads.

Enabling Transparent Huge Pages (THP) is **recommended** whenever **TFHE-rs** is used in production or for benchmarking.

To enable it on Linux, run:

```shell
echo always | sudo tee /sys/kernel/mm/transparent_hugepage/enabled
```

To make this persistent across reboots, add `transparent_hugepage=always` to the kernel command line (e.g. via GRUB).


---

# 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/configuration/system-tuning.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.