# How do I optimize the terminal to improve performance?

### **Method 1. Increase the price scale** 

This optimization method significantly reduces the amount of RAM consumed and has virtually no effect on the technical analysis functions. Additionally, a compressed DOM becomes much more convenient for trading when market volatility is high.

The price scale works as follows. For example, a BTCUSDT futures is open, and it has a price step of $0.01. If you set the price scale to 100, the price step for the BTCUSDT futures becomes $1. That is, the volumes at different price levels are combined into one level, and the volume of data is reduced by nearly 100 times.

To change the price scale in the **DOM window** or **Charts window**, click the **Price scale** icon on the tool panel, enter a new value and click **Apply**.

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80034158454/original/5Ivlf4aKwnrbLVC_eSxUOp1m7QXkt4UT2g.png?1630505554)

### **Method 2. Change data type from clusters to bars**

With this optimization method, the complete data set is not loaded, as it is with clusters. Instead, only the OHLC bar, volume, and delta is loaded from the server.

This method has some downsides: it's not possible to view clusters, and some volume indicators (Volume Profiles and Dynamic Levels) and the Volume Profile graphical object also do not work.

To change the data type, open the [timeframe selection](/english/settings/basic-setup/selecting-a-timeframe.md) window and change the data type to **Bars**.

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80034158712/original/LyTqORpbQrkRM0FMhpwG9PN-8-FGlRbv4Q.png?1630505578)

### **Method 3. Reduce the amount of downloaded history**

If you don’t need a chart with a deep history, you can set the maximum number of days that are shown for each timeframe. 

To adjust these settings, open the [timeframe selection window](/english/settings/basic-setup/selecting-a-timeframe.md) and click **Edit**. Next, for each preset timeframe, you can set the history depth in days separately for the **Charts window** and the **DOM window**. These settings are not automatically applied to all windows after editing. The timeframe must be selected again in each window.

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80034158879/original/eJ6cdc6-pML1ytdhnyY9lBZQHQPXfquodA.png?1630505609)

### Method 4. Use the latest version of the Tiger.com Windows terminal 

With each [update of the terminal](/english/platform-updates.md), its various components are optimized, including those related to downloading historical data. Starting from version 6.8, the pagination mechanic has been introduced in the terminal, which allows you to download historical data in "packages", which increases the speed of loading and displaying data in various windows of the trading platform.

### Method 5: Reduce the number of open windows in the terminal 

A large number of windows opened in the Tiger.com Windows terminal, especially those that are [linked to each other](/english/settings/basic-setup/linking-windows.md), increases the number of requests to the Tiger.com servers. Smaller and non-standard timeframes (30 ticks, 9 minutes, 43 hours, etc.) also affect the data acquisition speed. Reducing the number of these windows in the workspace and working with more "classic" timeframes (1 second, 5 minutes, 1 hour, 1 day, etc.) will increase the speed of loading historical data and displaying them in the terminal.


---

# Agent Instructions: 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:

```
GET https://support.tiger.com/english/frequently-asked-questions/how-do-i-optimize-the-terminal-to-improve-performance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.