> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/optimize-the-pentaho-system/performance-tuning.md). # Performance tuning You can use optimization tools to improve the speed and efficiency of the Pentaho products. This information also includes best practices and references for analysis, reporting, data integration, and data mining. Performance tuning is different from configuration. While initial configuration of your system involves logically setting up each Pentaho component for basic functionality, performance tuning aims to locate, identify, and remedy bottlenecks in your system performance. While configuration is typically completed when you initially set up your system, tuning is often performed in response to problems which arise during the preproduction and production stages. Each method described in this guide applies to a specific situation and should be properly evaluated for success in your system prior to implementation. Some of these performance tips remove functionality, and in some cases security, from the instance of your Pentaho Server. Others will assign more system resources to the Pentaho Server, which could in turn impact other services running on the same machine. You have to determine the best compromise between performance on one end and functionality, security, and resources on the other. {% hint style="info" %} **Note:** The tuning suggestions listed here are meant as an initial set of self-service tasks for improving the performance of the Pentaho Suite. More advanced techniques may improve performance, but require surgical changes to the code or software. These techniques are not included in this section for safety reasons. A Pentaho partner or consultant can assist you with more advanced performance improvements, if needed. {% endhint %} --- # 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.pentaho.com/pdia-admin/optimize-the-pentaho-system/performance-tuning.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.