> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/engineering-metrics/code-quality-metrics/performance.md). # Performance In code reviews, performance issues refer to things that can make a program run slower or use more resources than necessary.
These problems might come from using inefficient methods to do tasks, like sorting or searching data. They could also happen if the program uses up too much memory, takes too long to do calculations, or accesses a database too often and too slowly. Other common issues include having too much code doing the same thing or not handling multiple tasks at once efficiently. Catching and fixing these performance issues during code review is important to make sure the program runs smoothly and doesn't waste resources. By finding and improving areas where the program is slow or inefficient, developers can make it faster and more responsive for users. ### **Managing rules for security-type issues** You can manage these from the Settings > Code health > Rules.
You can filter these pre-defined rules based on severity, language, and type.\ Additionally, you have the option to toggle individual rules on and off to mark them as active or inactive.\ Once deactivated, the respective issue will no longer be highlighted during subsequent reviews. --- # 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://typo.gitbook.io/typo-help-docs/engineering-metrics/code-quality-metrics/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.