No surprises there. It's easy to see that this is happening by just watching the changes from the local database being sent to the app and things slow down as more and more campsites are added.
We've done the obvious view optimisation to use Html.keyed so the likely culprit is the sorting. I wonder if there's a quick optimisation we can do to speed this up. However, before we do that we should add some performance testing for this case.
Using the Chrome profiler over the initial load of data from the local database it looks like the Campsite.shortenName function is taking up 43% of the cpu time.
No surprises there. It's easy to see that this is happening by just watching the changes from the local database being sent to the app and things slow down as more and more campsites are added.
We've done the obvious view optimisation to use
Html.keyed
so the likely culprit is the sorting. I wonder if there's a quick optimisation we can do to speed this up. However, before we do that we should add some performance testing for this case.