On 11/29/13 4:47 AM, Robert Kaiser wrote: > Just for my understanding (I have commented to users with huge, e.g. > ~100MB sessionstore.js in bugs as well), I thought we were working on a > rewrite of session store anyhow that would not kepp info of all tabs in > one file? > > I think I have heard that we'd need to do this because of e10s anyhow at > some point, and that it also would help our startup if we didn't need to > load all session store data for all tabs at once but could do it per tab > when they are actually restored/loaded.
This redesign is bound to happen, sooner or later, although we are not actively working on this at the moment. It was blocked in part by the fact that the implementation of Session Restore had become a mess (that's now mostly solved) and by the fact that it was completely monolithic (also solved in many cases). I hope that we can now resume that work on Q1, but that's not a promise. Note tat this is actually not required by e10s, but if done well, this should indeed improve startup, as well as memory use. > Now I fully agree with trying to not store things we probably should not > keep anyhow, I just wonder if it might make sense to take into account > where session store is going. Well, any change that would split sessionstore.js is going to need even more effort in ensuring that we collect the garbage, so I believe that this is a useful first step. Cheers, David -- David Rajchenbach-Teller, PhD Performance Team, Mozilla _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
