Yes, but normally the GPU is specialized in doing this kind of graphic compositing with less power than the CPU. Otherwise, GPU acceleration would make no sense if there is no energy and performance benefit.
So the set-cpu-scaling-governor to performance is only useful if the graphic compositing is done completely by the CPU alone, which I doubt.
I didnât try this yet but same behavior with slower scrolling I notice today also in other apps which use TextArea (for example TinyEdit with opened file) and there is no delay in their qml code.
My observation was, that apps with no delays run faster after applying the tweak list, and apps that have their own delays in their qml code, stay slow or often donât launch any more until their delays also are reduced to 1/4, and some delays more.
Examples: File Browser, All Radio, LLs vPlayer, DeadBeef silica.
Others of my apps were not affected, they work as before but simply less time wasted for graphical effects.
For me it depends on the part of app⌠scrolling list of items is faster but where is long text as Tidings and Linksbag on page with article, scrolling is slower and stops every few line and without the fast scroll to bottom/top on the rightside.
What is Tidings and Linksbag, please? A Webpage?
But genarally said, thereâs a lot more to tweak than mentiond in the list, Iâll post all tweak lists I have as soon as possible. In the Browser, there is also a lot of about:config settings that can be teeaked/tuned to speed up Browser.
Astonishingly a tweak in
/usr/lib/qt5/qml/Sailfish/Office/PDFView.qml
affects the GUI generally.
https://openrepos.net/content/poetaster/tidings
Tidings is a news feed and podcast aggregator. Always be up to date with the latest news of what matters to you on your mobile device.
https://openrepos.net/content/maledictus/linksbag
LinksBag - this is an unofficial getpocket.com client with almost full implemented api. There is read mode too.
I recorded a short video where is Tidings app - scrolling list of articles is fast but when I open article and load full version of article, then scrolling long text is slower than without tweaks. I think itâs not app depend, but something in Sailfish/Silica affected by some tweak, because itâs same in app LinksBag and some my private apps (in which I donât have any delay in code) where are long texts. On the video itâs maybe looks like a little bit faster than in reality.
So itâs by this part. Today I tried to change it to 20000 and scrolling behaviour is back to normal, just faster than original, maybe too much 
and 12000-15000 would be more optimal.
diff -ruN original/usr/lib/qt5/qml/Sailfish/Silica/SilicaFlickable.qml patched/usr/lib/qt5/qml/Sailfish/Silica/SilicaFlickable.qml
--- original/usr/lib/qt5/qml/Sailfish/Silica/SilicaFlickable.qml
+++ patched/usr/lib/qt5/qml/Sailfish/Silica/SilicaFlickable.qml
@@ -60,7 +60,7 @@
pixelAligned: true
flickDeceleration: Theme.flickDeceleration
- maximumFlickVelocity: Theme.maximumFlickVelocity
+ maximumFlickVelocity: 2000
boundsBehavior: (pullDownMenu && pullDownMenu._activationPermitted) || (pushUpMenu && pushUpMenu._activationPermitted)
? Flickable.DragOverBounds : Flickable.StopAtBounds
Sorry for late response @Kuba77 , I tested right now and youâre right, 12000 and 20000 works significantly better. The 2000 I suggested was only by guessing, and itâs better/faster than original value.
BUT: neither with 12000 nor 20000, AllRadio doesnât work any more. With 2000 it works. All other apps work, and work faster with 12000 or 20000.
Any ideas why just AllRadio?
I donât know if itâs documented, but you can change the constants from the Theme, with dconf without patching files where they are used. For instance:
dconf write /desktop/sailfish/silica/maximum_flickVelocity 20000
will change the default value from 5000 to 20000 for the constant Theme.maximumFlickVelocity in QML. Possible entries are:
font_family
font_family_heading
font_size_tiny
font_size_extra_small
font_size_small
font_size_medium
font_size_large
font_size_extra_large
font_size_huge
item_size_extra_small
item_size_small
item_size_medium
item_size_large
item_size_extra_large
item_size_huge
icon_size_extra_small
icon_size_small
icon_size_small_plus
icon_size_medium
icon_size_large
icon_size_extra_large
icon_size_launcher
padding_small
line_width
horizontal_page_margin
button_width_small
button_width_extra_small
button_width_medium
button_width_large
page_stack_indicator_width
flick_deceleration
maximum_flickVelocity
Thanks @dcaliste , I executed the command and flicking is now really very snappy as I like it and AllRadio still playing!
Thanks for providing the possible dconf commands! 
But Q: will the dconf setting go lost, if I select an ambience that contains a maximum_flickVelocity?
edit: unfortunately AllRadio again stopped to work. So I had to set back to 2000 and reboot. Now AllRadio works again.
Basically, I donât know the answer. But on my device, none of the keys mentioned here were previously existing in DConf. So I guess, this capability exists but is not used by the ambiance mechanism.
I forgot to mention yesterday the usual warnings: if not documented it may disappear from a future release etc.
Indeed, setting the value with DConf is equivalent to set the value by patching.
Maybe also, if you want to remove the DConf entry, do:
dconf reset /desktop/sailfish/silica/maximum_flickVelocity
I donât think you can set that using an Ambience. Ambiences use a different DConf path/dir, namely /desktop/jolla/theme/ and /desktop/jolla/theme/color.
Have you made Ambiences that can do that?
@dcaliste , @nephros I was concerned because some new ambiences did overwrite my carefully adjusted sound configuration for the signal tones (phone rings, SMS, messenger, calender + clock alarm) that I made with cat, chicken and Spongebopâs Gary Miau, with other tones from the new ambience, and never set back the old tones when choosing an old ambience.
Regarding maximum_flickVelocity it was my mistake / error. There is no maximum_flickVelocity in ambiences. Iâm so sorry 
I donât think what QML calls Theme is the same as Ambience.
AllRadio hasnât been updated since 2018; I wouldnât worry about it. Alternatives exist for SFOS, even âAllradio2â in the official store.
Works like a charm & looks good
Thanks for the hint, didnât know that this brand new version. Iâm very happy that revival and that this wonderful app is now supported again!
edit: test condition: Xperia 10 / SFOS 5.0.0.68
Shit, again missed to put this topic into the community meeting for discussion. But even if itâs not really a new os part - perhaps it should be handed as some kind of pull request?
Iâm also somehow disturbed that no one from Jolla team said anything to all this do far. Perhaps we should also tag some of themâŚ
I put it into the topic for the next commu meeting on September 25th. Letâs waitâŚ
I linked this thread cause I donât know if I could make it into the meeting, but in fact every needed information can be found here, so all in all we just need an answer from Jolla if they are aware of this and why they did it or if itâs possible to implement such tweaks in general for future releases of SFOS.
Have reviewed version, but canât post because formatting as code doesnât work any more for me. Neither with three backticks nor with the </> button of the editor.
Qâs:
Only for me or also other users affected? Is this since the latest forum software update? What to do now? How can I now post as code?
Did you try to press the âSwitch to standard Markdown editor (Ctrl M)â on the top left of the toolbar of the reply box? It brings back the old editor and at least there on the preview the triple ticks works for me.
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Curabitur non neque sit amet felis laoreet maximus id id ipsum.
Etiam luctus tellus id hendrerit maximus.
Morbi viverra dui quis purus aliquet auctor.
Nullam scelerisque tortor vel est viverra, nec egestas risus faucibus.
Integer elementum erat ut nisi blandit viverra quis varius nisl.