# Performance Testing

## Testing Browser and CEF Rendering

Use the URLs below to test your hardware's rendering performance and overlay encoding pipeline. Ensure all outputs run smoothly at a constant 60fps. If you encounter frame drops or stuttering, consider upgrading your hardware. Using a GPU is recommended for smooth scrolling ticker animations.

* **Static Rectangle:** Basic first test for loading and rendering an output URL \
  <https://app.singular.live/output/5ZzzJADkEiSGsfZxxbltbJ/Output?aspect=16:9>
* **Moving Rectangle**: Basic horizontal animation should show a smooth animation on the output\
  <https://app.singular.live/output/7oTbGvhQYlmEHWIWE4NWCg/Output?aspect=16:9>
* **Static 20 Text Elements**: Loading and rendering HTML text\
  <https://app.singular.live/output/4BxIZCOM2J5PPgojAnZfRj/Output?aspect=16:9>
* **Static Example Graphics**: overlay containing text, images, basic widgets\
  <https://app.singular.live/output/6MAXCzTulkAyZlGPHfYJoM/Output?aspect=16:9>&#x20;
* **Pixel fill rate performance of CEF**: CPU-only systems will render only a few frames per second, and systems with GPU will render at 60fps!\
  <https://app.singular.live/output/3KM3hemkGlLdPfBrHVCXuK/Output?aspect=16:9>
* **Combined test**: Ticker running across the screen with a frame counter and an fps meter. We also added a color bar to check if pixel order is handled correctly. \
  <https://app.singular.live/output/6W76ei5ZNekKkYhe8nw5o8/Output?aspect=16:9> &#x20;


---

# 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://developer.singular.live/support/performance-testing.md?ask=<question>
```

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.
