Hello here! I would like to use Compose in one of ...

# compose

[gpaligot]

Hello here!
I would like to use Compose in one of my professionnel project with a large code base but I have a huge performance impact when I’m using a LazyColumn with a pretty simple row (a Row with some texts inside).

Attached to this message, you can find an example on a OnePlus 7T with the GPU usage overlay but it is worst on a Motorola G8 Plus where it is just not usable... We extracted the list on an external project where it is better but we have always a lag on some devices (Motorola G8 Plus impacted). Here the GitHub repository if some of you want to check the source code: https://github.com/adrienbusin/TestComposeLags

For information, yes the build is in debug but it is clearly not better with a release version...

21-11-16-15-16-20.mp4

[gpaligot]

Here the execution of the GitHub project in debug (the first app) and in release (the second app) on the Motorola G8 Plus.

XRecorder_16112021_153538.mp4

[gpaligot]

Here the execution of the first video but in release mode and on a OnePlus 7T. A little bit better but performance still not good.

21-11-16-15-44-56.mp4

[stojan]

Are you running a debug or release build?

might wanna take a look at this: https://engineering.premise.com/measuring-render-performance-with-jetpack-compose-c0bf5814933

[gpaligot]

Yes, like mentioned in my first message. Performance is bad in debug and release mode. First video is an example in debug, the last one in release. 😕

[Albert Chang]

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1630248475315600?thread_ts=1630247931.314700&cid=CJLTWPH7S

[gpaligot]

Thanks @Albert Chang, didn’t have the information about R8 builds but I think it isn’t normal to have this huge performance impact on debug and release mode. Some list can be used even in these modes without an optimized build and in my case, I show only a list with a Row and some texts... R8 build shouldn’t be necessary just to show 50 elements.

[Zoltan Demant]

@gpaligot Which version of compose are you using? I saw some issues myself.

[gpaligot]

1.0.5

[grandstaish]

I get 60fps in your sample app (even without any optimisations) so i'm assuming the problem hasn't been captured fully there. You could try adding a bunch of logs to your real code to see exactly what's being recomposed when you scroll (presumably it's a lot to see perf like this)

[Albert Chang]

Well it is normal in Compose UI.

[Zoltan Demant]

@gpaligot I think the regression started showing up after 1.0.4, theres a report of it here. In my case, about 3% of users notice it - most running on lower end devices, but Ive also seen it on a pixel 2 and 6.

[gpaligot]

@Zoltan Demant Thanks for your issue. It describes pretty well my performance issue. When I have more than one text inside a Row, performance is really bad.

[gpaligot]

@grandstaish My FPS seems pretty good too but the GPU usage is really bad, even with the sample app.

[gpaligot]

@Albert Chang Not sure why it is normal. 🤔

[eygraber]

Did you try a release build again with R8 enabled?

[gpaligot]

Yes, the performance is bad too. 😕

[Zach Klippenstein (he/him) [MOD]]

Please file a bug and link your sample project and data that you linked here. Tracker link is in channel topic

[Sergey Y.]

Try moving the initialization of listState below the list of items or wrap the last with remember block. 🤔
https://github.com/adrienbusin/TestComposeLags/blob/d142a51e8ae732659eb412c7e5a28e584fea1c05/app/src/main/java/com/decathlon/android/instore/android/testcompose/MainActivity.kt#L21

[Sergey Y.]

I'm not sure, but it might involve the recomposition process here.
LazyList state holds a bunch of parameters that update during list scroll, which would cause a recomposition of that composition group(underhood Compose machinery).
Therefore, you recreate the entire list with items every time the LazyList state updates.

[Sergey Y.]

I have a test project to track the performance of the most popular Compose components. Among them is LazyList. And I did not notice any problems there.

[Zoltan Demant]

@Sergey Y. If you have the time for it - try attaching Modifier.clickable to items in a list in your test project, the underlying focus behavior seems to be whats causing issues.

[Sergey Y.]

@Zoltan Demant I have a click listener there too https://github.com/desugar-64/android-compose-performance-test/blob/main/android-c[…]t/app/src/main/java/com/sergey_y/simpletweets/ui/tweet/Tweet.kt

[Zoltan Demant]

@Sergey Y. Great! I saw that youre using const val compose_version = "1.0.4", if you upgrade it to 1.0.5 and above, I think you will see way more lag when using the lists (Im running on 1.1.0-beta02)

[Sergey Y.]

I have tests for every compose version

[Sergey Y.]

you can switch the branch or see the reports in the repository

[Sergey Y.]

opps, I didn't push the rest branches