torstai 28. marraskuuta 2013 13.56.13 UTC+2 David Rajchenbach-Teller kirjoitti:
> As many of you know, Session Restore is something of a performance hog,
> for many reasons - we have reports of. One of the reasons is that we
> store so very many things in sessionstore.js and sometimes keep stuff
>
On 28.11.2013 16:15, Honza Bambas wrote:
On 11/28/2013 12:56 PM, David Rajchenbach-Teller wrote:
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very many things in sessionstore.js and
On 11/28/2013 6:15 PM, Matthew N. wrote:
On 11/28/13, 7:15 AM, Honza Bambas wrote:
On 11/28/2013 12:56 PM, David Rajchenbach-Teller wrote:
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very
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
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very many things in sessionstore.js and sometimes keep stuff
for a very long time.
As part of bug 943352 followup, we are considering
On Thu, Nov 28, 2013 at 11:56 AM, David Rajchenbach-Teller
dtel...@mozilla.com wrote:
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very many things in sessionstore.js and sometimes keep
On 11/28/13 1:33 PM, Till Schneidereit wrote:
This would all be tackled after we did other things like getting rid
of all history entries for iframes, which won't be restored in any
case, right?
We're not sure about the relative priorities of this cleanup vs.
removing the history entries for
On Thu, Nov 28, 2013 at 1:55 PM, David Rajchenbach-Teller
dtel...@mozilla.com wrote:
On 11/28/13 1:33 PM, Till Schneidereit wrote:
This would all be tackled after we did other things like getting rid
of all history entries for iframes, which won't be restored in any
case, right?
We're
On 11/28/2013 12:56 PM, David Rajchenbach-Teller wrote:
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very many things in sessionstore.js and sometimes keep stuff
for a very long time.
As
On 11/28/13, 7:15 AM, Honza Bambas wrote:
On 11/28/2013 12:56 PM, David Rajchenbach-Teller wrote:
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very many things in sessionstore.js and
On 11/29/13 12:15 AM, Matthew N. wrote:
On 11/28/13, 7:15 AM, Honza Bambas wrote:
On 11/28/2013 12:56 PM, David Rajchenbach-Teller wrote:
As many of you know, Session Restore is something of a performance hog,
for many reasons – we have reports of. One of the reasons is that we
store so very
David Rajchenbach-Teller schrieb:
As part of bug 943352 followup, we are considering automatically
cleanup some of the contents of sessionstore.js.
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
12 matches
Mail list logo
