This repository was archived by the owner on Oct 28, 2026. It is now read-only.
Repository navigation
Docs: cast figures re-measured - #246
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The cast figures in the runtimes table and the cast guide, re-measured on a Roku TV (OS 15.3.4). Each run was 40 s through
tools/run_cast_example.py, with CPython 3.14.6 on Windows, MicroPython 1.30.0-preview on unix and Windows, and the P4 4" panel.Values are frames a second, as (testris, lv_test_timer).
python(Linux)python.exemicropython(unix)micropython.exeThe desktop range in the guide goes from 6 to 10 to 8 to 14. A P4 Companion frame at 480x270 took 266 to 294 ms to show, not about 180 ms, so the guide now says the P4's limit is PNG encoding.
Some figures are unchanged:
These weren't re-measured: