> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-gateway/4/optimize-performance/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Optimize Gateway performance

> Configure your Gateway instance for optimal performance based on performance testing results.

This article guides you through configuring your Gateway instance for optimal performance based on performance testing results.

## Configure server threads

Gateway lets you customize the number of server threads available on your instance. You can view your current thread configuration in the System Configuration UI under the **HTTP Server Threads** setting.

![](/_fern-img/9ab792e8f7f531df03366da4bcfff15163d6e208772c2e036542716a71e82f48.webp)

You cannot edit System Configuration settings in the UI. To update this value, modify Gateway's `properties.yml` configuration file.

In the `properties.yml` file, locate the `http_server_threads` value. Performance testing shows the optimal value is 4x the number of cores on your server. For example, if your Gateway server has 16 cores, set `http_server_threads` to 64.

## Configure adapters

You can optimize performance when you configure your Gateway adapter by adjusting the following settings.

![](/_fern-img/a9751d1b5cba68a5b32e2ba9cf0b74e25ca080bee0807e5ca2dff98cb23df255.webp)

### Set healthcheck type to startup

We recommend setting the healthcheck type to **startup**. Healthchecks don't affect response time or execution performance of Gateway calls. However, intermittent healthchecks can cause unnecessary errors if the healthcheck fails.

### Disable throttling

Performance testing shows adapter throttling provides no performance benefits. Disable throttling to reduce complexity when making Gateway calls.

> Configure your Gateway instance for optimal performance based on performance testing results.