Updated: March 11, 2025 |
This chapter describes the graphics configuration options to adjust the performance of your QNX cloud target.
The cloud and hardware targets both use the same graphics subsystem; hence, the targets share the same binaries such as standard shared objects, utilities, and screen commands.
screen -c /usr/lib/graphics/software-rendering/other_graphics.confThen test your configurations on your target with a graphics application; for example:
gles2-gears -display=1 gles2-gears -display=2
[Processor] ## Number of threads used by the scheduler (0 interpreted as "min(max_cpus_available, 16)") # ThreadCount = 0 ThreadCount=4 ## Core affinity used by the scheduler # AffinityMask=0x1 # AffinityMask=0xFFFFFFFFFFFFFFFF AffinityMask=0xF000 ## "any": threads can use any of the cores available in the affinity mask # (default) AffinityPolicy="any" ## "one" : threads can only ever use one of the cores available the affinity mask # AffinityPolicy="one"
To support other custom modes, you can customize the Wfdcfg library; for details, go to the Building the Wfdcfg library chapter in the OpenWF Display Configuration Developer's Guide.
The webrtc-server-iosock process handles the entire display framebuffer (i.e., read, encode, packetize, and transmit).
webrtc-server-iosock --format=rgb565The default RGB565 should be the most efficient.
webrtc-server-iosock --scale=1/2While scaled down, the web client retains the resolution in the Screen configuration file.