when set forceNonDeterministicRendering={true}, mistake in performance occurred :( about recyclerlistview HOT 4 CLOSED

You layout looks deterministic to me. All items seem to be of fixed size. In any case, non deterministic shouldn't be much slower. There could be three things which are wrong:

1. Estimates dimensions are nowhere near the actual ones. This seems to be the case since your deterministic render looks way different.
2. Missing shouldComponentUpdate in your component which the rowRenderer returns. Very important for non deterministic scenario.
3. rowHasChanged in dataProvider has an invalid check that returns true most of the time. Most likely this is not the problem since deterministic mode is fast for you.

from recyclerlistview.

please clarify, what is role of shouldComponentUpdate, rowRender, and rowHasChanged in performance of RecyclerView?
again, thank you very much

from recyclerlistview.

In case of non deterministic rendering RecyclerListView will render a few times for than regular. These cycles are to reposition items after actual render. Since the whole tree will re-render with the listview rowHasChanged and shouldComponentUpdate make sure that your items don't. RecyclerListViews self render is pretty cheap. Having these checks prevents your item from being rendered unnecessarily which significantly reduces JS overhead.

from recyclerlistview.

Inactive for a while. Closing.

from recyclerlistview.