Replies: 1 comment 1 reply
-
@pdpino @hoangnm the performance issues being experienced here and in #259 is due to the VirtualizedList. If you use your old library version from 2 years ago without VirtualizedList, the performance and speed is much better. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem
The component may run into performance issues when rendering too many days/weeks, and/or too many events. For example this happens with 500 evts:
demo-500-evts-2022-05-24_23.47.01.mp4
Possible causes
events
prop changes --> allEvent
s are re-rendered (e.g. when dragging an event)goToDate()
), many pages have to be added to the lists (see for example: onSwipeNext stuck #207)(I've been using android systrace for profiling, but is still a limited tool)
What now
I've been trying to improve these, not only for performance, but also for other features, for example:
VirtualizedList
represents one page ofnumberOfDays
(e.g. 7 days)numberOfDays
changes, the items must be recalculated and re-rendered from scratch to align items with pages (even though the events are the same). (SeecomponentDidUpdate()
here)numberOfDays
would not require recalculating the items<MonthView>
component (Month View. #95) with these considerations in mind@hoangnm any thoughts? I'll probably be submitting some PRs
cc: @rdewolff, @Salmankhan033, @Vidxyz
Beta Was this translation helpful? Give feedback.
All reactions