> For the complete documentation index, see [llms.txt](https://docs.allout.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allout.game/going-all-out/improving-performance.md).
# Improving Performance
### Loading Performance
Game load times are primarily determined by the size of the assets in your project.
* Mipmaps (1/8 resolution versions of your textures) are included in the initial game payload
* Textures used by Sprite\_Renders with "Wait for Load" checked will block loading waiting for high resolution versions (should only be used for spawn areas)
* Other high resolution textures are streamed and loaded after join
{% hint style="warning" %}
We currently include mipmaps of every asset in your res directory even if you don't include it in the scene which can affect load performance if you have large unused assets.
{% endhint %}
### Client Performance
You can press **F3** at any time to open a client profiler. Check the "Capturing" checkbox to start recording and uncheck it to pause and review.
On gaming PCs we recommend targeting \~2ms total frame times. This will give you headroom for low end mobile devices which will typically be 4-6x slower.
### Network Performance
Basically: reduce the number of entities in your scene doing stuff. We'll add more guides here soon :D
---
# 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.allout.game/going-all-out/improving-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.