> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/frequently-asked-questions/how-do-i-optimize-the-terminal-to-improve-performance.md). # How do I optimize the terminal to improve performance? Optimizing your terminal configuration can significantly improve your experience when working with the platform. Proper optimization can help: * Reduce the time required to open and load new windows. * Ensure smooth real-time quote updates without lag. * Speed up the loading of historical chart data. Slow terminal performance is usually caused by insufficient RAM, limited CPU performance, or graphics card limitations. This article describes several ways to reduce resource consumption and improve overall terminal responsiveness. ### **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) ### Enable Automatic Data Type Selection Tiger.com Terminal supports a wide range of popular indicators. Depending on the selected indicator, the terminal may request either Bar data or Cluster data. To avoid selecting the required data type manually, enable **Automatic Data Type Selection** in: **Settings → General Settings → Chart** Cluster data requires significantly more memory because of the larger volume of information being processed. It also takes longer to load compared to standard bar data. Bar data is much less resource-intensive. Therefore, it is important to prevent the terminal from loading cluster data when it is not required. #### How Automatic Data Type Selection Works When a chart or indicator is opened, the terminal automatically determines which data type is required for that particular element. For example: * If you open a candlestick chart and apply the **Volume** indicator through the Indicator Manager, the chart will use **Bar** data. * If you open a Cluster Chart and apply the **ClusterSearch** indicator, the chart will use **Cluster** data. This allows the terminal to load only the data necessary for the selected chart and indicators, reducing unnecessary resource consumption. For more information about available chart loading methods, refer to the corresponding article in our Knowledge Base. *** ### Reduce the Amount of Historical Data Loaded The less historical data the terminal needs to download and process, the fewer system resources it will consume. You can reduce the amount of loaded history by specifying a start date in the timeframe settings of a chart or DOM window. > **Note:** When charts are loaded directly from an exchange, setting a start date may not reduce the amount of downloaded data because exchanges often provide a fixed number of historical bars. Using lower or custom timeframes (such as 30 ticks, 9 minutes, or 43 hours) may also affect loading speed. For faster loading and smoother performance, consider using more standard timeframes, such as: * 1 second * 5 minutes * 1 hour * 1 day These timeframes are generally processed more efficiently and can significantly improve the speed of historical data loading and rendering. *** ### Reduce the Number of Open Windows and Indicators A large number of open windows, especially linked windows, increases the number of requests sent to Tiger.com servers. The fewer requests the terminal generates, the faster historical data can be loaded and displayed. As mentioned earlier, cluster data has a significant impact on memory usage. In addition, some indicators that process large amounts of data—such as **ClusterSearch** and **Volume Profiles**—can place substantial load on both the CPU and GPU. To reduce resource consumption, consider removing such indicators from inactive charts. Combined with Automatic Data Type Selection, this allows inactive windows to use standard bar data instead of cluster data, while also reducing CPU and GPU workload. ### 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. ### Manually Clear Memory Starting from version **6.9**, Tiger.com Terminal includes the ability to manually trigger garbage collection, helping the application release unused memory more efficiently. To run memory cleanup manually: **File → Clear Memory** Memory cleanup is performed automatically by the terminal according to an internal algorithm. However, if you notice that the terminal becomes less responsive over time, manually clearing memory may help improve performance, especially if available RAM is running low. *** ### Reduce Configuration Auto-Save Frequency When auto-save is enabled, the terminal periodically creates backup copies of your configuration files. These backups can later be restored through: **File → Configuration → Restore** While useful, the auto-save process consumes CPU resources. If auto-save occurs too frequently, it may negatively affect performance on systems with limited processing power. To reduce the load, consider increasing the auto-save interval: **Settings → General Settings → Miscellaneous** Using a longer auto-save interval reduces the frequency of backup operations and lowers overall CPU usage. *** ### If the Above Steps Do Not Help If you have tried all of the recommendations above and the terminal still performs slowly, the issue may be related to your computer hardware or operating system. We recommend: * Running a full antivirus scan. * Ensuring that your operating system is fully updated. * Installing the latest available Windows updates. * Verifying that your computer meets the minimum system requirements for running Tiger.com Terminal. #### Contact Support If the issue persists, please send the following information to our support team at : * Your configuration file (available through **File → Configuration → Save**). * A screenshot of **Help → About**. * Your computer specifications and operating system version. * A detailed description of the issue, including when and under what conditions the slowdown occurs. * A video recording demonstrating the behavior, if possible. Providing this information will help us investigate the issue and identify potential causes more quickly. --- # 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://support.tiger.com/english/frequently-asked-questions/how-do-i-optimize-the-terminal-to-improve-performance.md?ask=&goal= ``` `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.