# Performance ## Keep frame rates low Keep frame rates above 30fps. When viewers switch from high frame-rate experiences to low frame-rate experiences, they often don’t have words to describe the loss in quality, but can tell that something doesn’t look right. In short: low frame rates ruin the illusion. This can be challenging as Looking Glass renders 45 simultaneous views per frame. This is an expensive operation when not managed properly. If using Unity, use the [Rendering Statistics](https://docs.unity3d.com/Manual/RenderingStatistics.html) window to keep tabs on the following. ## Keep poly count low The ballpark range of the upper limit of polygons the system can render on a typical high end gaming computer is about 200k to 300k polys. This guideline can be bent under certain contexts as long as the final experience is tested. ## Keep draw call batches low Having many different textures on different objects under many different lights will multiply out to be many different draw call batches. If frame rates are too high, try unifying the lighting and textures to lower the batch count. ## Draw only what's important Make sure to disable any unnecessary scene elements to only render what is important. ## Use view interpolation The HoloPlay Unity Plugin View Interpolation will skip intermediate renders (and interpolate from captured renders), lowering computation cost. This can be used to increase performance. --- # 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://lfdocs.lookingglassfactory.com/keyconcepts/3d-design-guidelines/performance.md?ask= ``` 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.