STM32MP1 Browser Performance: Difference between revisions
From Wiki-DB
Jump to navigationJump to search
Fgerstandl (talk | contribs) |
Fgerstandl (talk | contribs) |
||
| Line 12: | Line 12: | ||
* many web controls for many purposes | * many web controls for many purposes | ||
[[File: | [[File:bardiagramIgnite.png|frameless]] | ||
It takes approx.3 seconds from menu click until content is fully visible | It takes approx.3 seconds from menu click until content is fully visible | ||
Revision as of 13:03, 1 June 2021
Tasks of the GPU
- For „simple“ webpages without 3D-features, the GPU is only used for „blitting“during a process step called „Raster(ization) and Compositing“
- „blitting“ = fast copy and move of memory objects
- By this, a strong relief of the CPU can be achieved
- this should be well possible with the STM32MP1
Performance Tests
"Infragistics Ignite UI" Demo Application
- commercial WebUI framwork based on Angular
- many web controls for many purposes
It takes approx.3 seconds from menu click until content is fully visible
QOpenGLWidget Example
Line-Chart Demo Application
with GPU
https://www.dropbox.com/s/323nv90lhp9wh02/mit_GPU.MP4?dl=0
no GPU
https://www.dropbox.com/s/kprvgowf8kzod6a/ohne_GPU.MP4?dl=0
DH demo from tradeshow
Webgl example (aquarium)
Functional GPU testing
Some Toughts about Javascript performance
Profiling with Chromium
Brief summary
- Webapplications must be optimized for particular embedded system resp. SOC
- Comprehensive analysis and profiling tools are available
- Thus, appealing web pages on embedded systems should be possible
- … where also the “responsiveness" is given
