I noticed that TopStoriesFeed does some work during startup even though the page is showing discovery stream: - register with SectionsManager - read/write with PersistentCache (might be addressed with bug 1544052) - network requests for endpoints - loading PersonalityProvider and other jsms - transforming stories Only the first item should be necessary right now. The others are probably unnecessarily slowing down the rest of startup. The complicated part is probably how to correctly initialize TopStoriesFeed if it actually needs to do stuff.
Bug 1544578 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I noticed that TopStoriesFeed does some work during startup even though the page is showing discovery stream: - register with SectionsManager - read/write with PersistentCache (might be addressed with bug 1544052) - network requests for endpoints - loading PersonalityProvider and other jsms - transforming stories Only the first item should be necessary right now (with the implementation in bug 1533601). The others are probably unnecessarily slowing down the rest of startup. The complicated part is probably how to correctly initialize TopStoriesFeed if it actually needs to do stuff.
I noticed that TopStoriesFeed does some work during startup even though the page is showing discovery stream: - register with SectionsManager - read/write with PersistentCache (might be addressed with bug 1544052) - network requests for endpoints - loading PersonalityProvider and other jsms - transforming stories Only the first item should be necessary right now (with the implementation of bug 1533601). The others are probably unnecessarily slowing down the rest of startup. The complicated part is probably how to correctly initialize TopStoriesFeed if it actually needs to do stuff.