Re:Why new Firefox 13 'load tabs on demand' is bad UX.
by illumen on Tuesday June 05, 2012 @02:05PM
(#4069893)
Interesting.
Putting in the work to just improve the speed is the hard fix usually. But I guess firefox and chrome are fairly optimized for loading already.
However, some good heuristics might help. Things like number of tabs, most common tabs used, active tab, time to load and responsiveness(frame rate, latency etc) would be good indicators.
I'm not sure how good hard coding stuff in like number of tabs would be. Whilst just loading up to 8 tabs would probably work, these numbers seem to change over time. Like the oldIE 4 connections limit for example. But! With frequent automatic updates, this value could be tweaked later if needed.
Cpu, and IO could be set based on the indicators as well.
Putting in the work to just improve the speed is the hard fix usually. But I guess firefox and chrome are fairly optimized for loading already.
However, some good heuristics might help. Things like number of tabs, most common tabs used, active tab, time to load and responsiveness(frame rate, latency etc) would be good indicators.
I'm not sure how good hard coding stuff in like number of tabs would be. Whilst just loading up to 8 tabs would probably work, these numbers seem to change over time. Like the oldIE 4 connections limit for example. But! With frequent automatic updates, this value could be tweaked later if needed.
Cpu, and IO could be set based on the indicators as well.