We profiled this with Florian, and it ends up that Repeater is no longer creating the bunch of components and then renders, but it creates each delegate asynchronously after which it renders each of them separately. So instead of a 1000 block create then render we have 1000 create + render, and sniffed rendering between creates slows down the things. This will always happen when page is loaded asynchronously and the loaded page has a Repeater, until upstream does something with the Repeater to load faster.
Using ListView with a cache to fit the whole model content behaves differently, at least the visible items are created in a block synchronously then rendered, and the rest of the invisible ones are created asynchronously afterwards. So this may be a better approach for use cases we have in the attached example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510201 Title: AdaptativeLayout take longer to show a page To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
