Repository navigation
Replies: 3 comments 1 reply
|
I migrated to v3 too as so far not much diff. Just with rapid change of v3 how to know which version is stable for prod use? Perhaps I should stick to v2 for now? |
0 replies
|
@Nezz Thank You for the great report as always.
Let's keep coordinating on this. These first impressions were very sensible. |
1 reply
|
Nice let‘s keep coordinating where necessary
…On Mon 19 Oct 2026 at 11:18, Adam Kapos ***@***.***> wrote:
Thanks! For now, I'm sticking to V2 with our custom patch that moves
rendering to a separate worklet, but V3 is clearly headed in the right
direction.
—
Reply to this email directly, view it on GitHub
<#4187?email_source=notifications&email_token=AACKXVRHTJRM5NVTVPP6KAD5UXL4TA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGM3DMOBRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19036681>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKXVVVGWUJFY264TD3HNT5UXL4TAVCNFSNUABIKJSXA33TNF2G64TZHM2DENJYGQ2TGMRVHNCGS43DOVZXG2LPNY5TCMBZHA3DOMRUUF3AE>
.
You are receiving this because you commented.Message ID:
<wcandillon/react-native-skia/repo-discussions/4187/comments/19036681@
github.com>
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi William! Thanks for the great work with V3, the multithreading support is exactly what I need for my projects.
I wanted to share some feedback, hopefully it'll be useful.
Context:
(
SkiaGraphiteView+SkGraphiteContext)What works well:
Issues I came across:
1. iOS: the display link caps at 60 Hz and pauses after every frame
SkiaView.mmcreates itsCADisplayLinkwithout apreferredFrameRateRange, so ProMotion devices never go past 60 fps.It's also paused whenever
presentFramefinds an empty queue, so in steady state it pauses and restarts every tick.2. Android: recording and presenting alternate instead of overlapping
RNSkGraphiteProducer::kickLockedreturns early while a frame is in flight or waiting to present, so a new framecan't be recorded while the previous one waits for vsync. At high refresh rates the picture rate gets cut in half: my Galaxy A55 got
64 fps where V2 managed 124.
3. Android: the frame callback is only armed on submit
FrameSchedulerposts the Choreographer callback only when a recording is submitted, so a recording that landsmid-frame waits a whole extra vsync.
4. Lazy pipeline compiles block the main thread at first use
The first present that needs a new pipeline blocks the main thread for as much as 700ms. Is it possible to precompile?
5. Every view's recorder re-uploads CPU images
Each view gets its own
Recorder, and with it its ownImageProvider, so app-lifetime CPU images get uploaded to theGPU again for every new view. The uploads seemed to outlive the recorder, with memory climbing by about 1.4 MB on
every screen open.
6. Skia objects shared into a worklet runtime are only freed by that runtime's GC
An idle runtime almost never GCs, so native state piles up: about 5.5 MB is allocated per screen open.
7. Smaller things
So overall iOS looks promising with some outstanding issues, whereas Android (which was already the problematic one) seems worse right now than V2.
I think some of these issues are being worked on, but I'd be interested in which ones are worth reporting properly. Thanks again!
All reactions