STM32MP1 Browser Performance - Revision history

Fgerstandl: /* "Infragistics Ignite UI" Demo Application */

2021-08-23T07:56:43Z

"Infragistics Ignite UI" Demo Application

← Older revision		Revision as of 09:56, 23 August 2021
Line 10:		Line 10:

	To get some insights the chromium profiling was used.		To get some insights the chromium profiling was used.


	[[File:ChromeProfilingIgnite.png\|frameless]]		[[File:ChromeProfilingIgnite.png\|frameless]]
	~~The~~ Chrome Profiler ~~shows~~ following ~~things~~:
			With the Chrome Profiler one can make following conclusions:
	* the CPU does most of the work		* the CPU does most of the work
	* there is no obvious point where CPU cycles would be spent excessively (perf doesn't indicate anything).		* there is no obvious point where CPU cycles would be spent excessively (perf doesn't indicate anything).

2021-08-23T07:55:19Z

Webgl example (aquarium)

← Older revision		Revision as of 09:55, 23 August 2021
Line 34:		Line 34:
	=== Webgl example (aquarium) ===		=== Webgl example (aquarium) ===
	http://webglsamples.org/aquarium/aquarium.html?numFish=1&canvasWidth=800&canvasHeight=480		http://webglsamples.org/aquarium/aquarium.html?numFish=1&canvasWidth=800&canvasHeight=480

	[[File:Webgl aquarium.png\|frameless]]		[[File:Webgl aquarium.png\|frameless]]

2021-06-02T07:44:00Z

@@ Line 1: / Line 1: @@
 == Performance Tests with hardware acceleration (etnaviv) ==
 === "Infragistics Ignite UI" Demo Application ===
@@ Line 184: / Line 178: @@
   =======================================================
 |}
 == Some Toughts about Javascript performance ==

2021-06-02T07:28:23Z

Performance Tests with software renderning (without GPU)

← Older revision		Revision as of 09:28, 2 June 2021
Line 71:		Line 71:

	The cube does not even show up on the screen.		The cube does not even show up on the screen.

			=== Conclusion ===
			Software Rendering (with no GPU) is no option on the STM32MP1 for graphical webinterfaces were responsiveness is required.

	== drawElements Quality Program (deqp) ==		== drawElements Quality Program (deqp) ==

2021-06-02T07:25:40Z

Performance Tests with software renderning (without GPU)

← Older revision		Revision as of 09:25, 2 June 2021
Line 64:		Line 64:
	* < 1 fps		* < 1 fps
	* too slow to be usable		* too slow to be usable

			=== 3D-animation and video as texture ===
			[[File:3danimation.png\|frameless]]

			https://www.dropbox.com/s/323nv90lhp9wh02/mit_GPU.MP4?dl=0

			The cube does not even show up on the screen.

	== drawElements Quality Program (deqp) ==		== drawElements Quality Program (deqp) ==

2021-06-02T07:24:19Z

Performance Tests with hardware acceleration (etnaviv)

← Older revision		Revision as of 09:24, 2 June 2021
Line 43:		Line 43:

	Running a webgl example page (fishtank) on the STM32MP1 (etnaviv) with Chromium under a resolution of 800x600 results in '''3fps'''.		Running a webgl example page (fishtank) on the STM32MP1 (etnaviv) with Chromium under a resolution of 800x600 results in '''3fps'''.

			=== 3D-animation and video as texture ===
			[[File:3danimation.png\|frameless]]

			https://www.dropbox.com/s/323nv90lhp9wh02/mit_GPU.MP4?dl=0

			The cube runs very smooth with at least 40fps.

	=== Conclusion ===		=== Conclusion ===

2021-06-02T07:10:05Z

Conclusion

← Older revision		Revision as of 09:10, 2 June 2021
Line 45:		Line 45:

	=== Conclusion ===		=== Conclusion ===
	Webapplications must be optimized for particular embedded system resp. SOC. ~~Appealing~~ web pages with responsive requirements on the STM32MP1 are possible.		Webapplications must be optimized for particular embedded system resp. SOC. Heavy WebGL applications are not suited for this platform.<br>
			Nevertheless appealing web pages with responsive requirements on the STM32MP1 are possible.

	== Performance Tests with software renderning (without GPU) ==		== Performance Tests with software renderning (without GPU) ==

2021-06-02T07:03:47Z

← Older revision		Revision as of 09:03, 2 June 2021
Line 221:		Line 221:
	:The performance profile gives you an overview over all important stats at once. You can record it while browsing through an website on the target.<br>		:The performance profile gives you an overview over all important stats at once. You can record it while browsing through an website on the target.<br>
	:You can save such profiles and import it with any other chrome browser to analyse the profile offline.		:You can save such profiles and import it with any other chrome browser to analyse the profile offline.

	~~== 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

2021-06-02T07:02:55Z

Conclusion

← Older revision		Revision as of 09:02, 2 June 2021
Line 45:		Line 45:

	=== Conclusion ===		=== Conclusion ===
	Webapplications must be optimized for particular embedded system resp. SOC		Webapplications must be optimized for particular embedded system resp. SOC. Appealing web pages with responsive requirements on the STM32MP1 are possible.

	== Performance Tests with software renderning (without GPU) ==		== Performance Tests with software renderning (without GPU) ==

2021-06-02T06:58:58Z

Performance Tests with hardware acceleration (etnaviv)

← Older revision		Revision as of 08:58, 2 June 2021
Line 43:		Line 43:

	Running a webgl example page (fishtank) on the STM32MP1 (etnaviv) with Chromium under a resolution of 800x600 results in '''3fps'''.		Running a webgl example page (fishtank) on the STM32MP1 (etnaviv) with Chromium under a resolution of 800x600 results in '''3fps'''.

			=== Conclusion ===
			Webapplications must be optimized for particular embedded system resp. SOC

	== Performance Tests with software renderning (without GPU) ==		== Performance Tests with software renderning (without GPU) ==