Originally posted by QwertyChouskie
View Post
Announcement
Collapse
No announcement yet.
Purism Shows Off The Librem 5 Linux Smartphone In Action
Collapse
X
-
Originally posted by tildearrow View PostOK, so I watched the video... and I have one big complaint.
Where is my 60FPS scrolling?
Are widgets being drawn on the CPU, or is the GPU this weak?
It doesn't look smooth as a 2019 smartphone. It looks like an early smartphone from the 2000's.
2. Currently Pixman doesn't even have accelerated codepaths for aarch64. There's already a patch for that being incorporated to PureOS, but the videos were made before that happened.
3. There's some small glitch somewhere in the kernel which makes everything incorrectly vsynced to 55Hz (the display is 60Hz), leading to tearing even though otherwise it would be perfectly smooth. It will be fixed.
4. WebKitGTK so far has seen only moderate amount of attention when it comes to tuning it for good performance on mobile. There's still a lot that can be done there.
5. There's also a lot of low-hanging fruits in compositor (phoc) when it comes to rendering optimization and input latency minimization. It just hasn't been done yet due to other things being higher priority for now
This phone will become faster over time.Last edited by dos1; 29 September 2019, 02:10 PM.
- Likes 4
Comment
-
Originally posted by dos1 View Post
1. Indeed, GTK3 draws its widgets with CPU. GPU acceleration comes with GTK4, which isn't released yet.
Originally posted by dos1 View Post2. Currently Pixman doesn't even have accelerated codepaths for aarch64. There's already a patch for that being incorporated to PureOS, but the videos were made before that happened.
Originally posted by dos1 View Post3. There's some small glitch somewhere in the kernel which makes everything incorrectly vsynced to 55Hz (the display is 60Hz), leading to tearing even though otherwise it would be perfectly smooth. It will be fixed.
- KWin uses a freaking timer
- RetroArch devs set the default rate to 59.95Hz, 0.01Hz higher than the NTSC standard 59.94Hz
- Compiz also uses a timer
- mplayer only uses a single thread for playback which pretty much means you'll have to go through constant audio desync/extreme catch-up
- KDE still draws some of its animations in 30Hz! And I have not figured out how to change that rate.
Originally posted by dos1 View Post4. WebKitGTK so far has seen only moderate amount of attention when it comes to tuning it for good performance on mobile. There's still a lot that can be done there.
Originally posted by dos1 View Post5. There's also a lot of low-hanging fruits in compositor (phoc) when it comes to rendering optimization and input latency minimization. It just hasn't been done yet due to other things being higher priority for now
Originally posted by dos1 View PostThis phone will become faster over time.
- Likes 1
Comment
-
Originally posted by tildearrow View Post
Wow. I thought GTK+3 already brought some sort of GPU acceleration but after seeing this I pretty much can say it's similar to Qt 5 in this regard...
I would like to see a video of its performance after the patch.
You must be kidding, right? Why can't open-source get fluid video right?
- KWin uses a freaking timer
- RetroArch devs set the default rate to 59.95Hz, 0.01Hz higher than the NTSC standard 59.94Hz
- Compiz also uses a timer
- mplayer only uses a single thread for playback which pretty much means you'll have to go through constant audio desync/extreme catch-up
- KDE still draws some of its animations in 30Hz! And I have not figured out how to change that rate.
I see.
They need to raise the priority of performance improvements as doing these may improve battery life.
I know.
Comment
Comment