This is a request to help me get the most out of turbo mode... hopefully others will find this worthwhile. Situation: I use a dial-up connection to connect to the Internet. However, I get tired of slow start-up times for Mozilla while I am online because when I am online I tend to do a lot of web browsing. I could turn on turbo mode, but then, when I am offline doing memory-intensive work, I will lose performance. And yes, I could leave one Mozilla window open the entire time I am online, but this clutters the screen when I am not browsing, and have several other TCP/IP apps open. Possible Solution: A compromise I would like is to have a turbo-mode pref allowing turbo mode to be on when I am online, turbo mode off when offline. This would make Mozilla much quicker when I really need it, without the penalty when offline (usually don't use it). This could easily be extended to other connection types, but I believe that the biggest gains will be for dial-up, since I'd venture that computers using dial-up are less likely to be high-end performers. Note that this could lead to somewhat chaotic loading/unloading behavior on systems with multiple connections, or in situations where the connection is lost and a new one immediately requested. A configurable delay could fix this on a per system basis.

This would presumably depend on bug 76111...

marking p3 and future

-> default assignee

Nominiating for nsbeta1, as QL will be on by default in MachV, and we should try an d optimize for the users memory resources (i.e. Only call upon resources when the functionality is needed).

We have no plans to introduce any additional options to the QL feature for MachV.

I've filed bug 131492 to enable Turbo after first use only. It could be a partial solution for this one. Also, bug 131492 should be easier to implement as well.

=> WONTFIX - turbo is gone after SM v1.1