Could we stat at memory-model=hight and then change our memory model mid-flight if there are any large, non-chrome, memory hungry processes?
-- Elliot On Wed, Jun 24, 2009 at 9:39 AM, Ian Fette<[email protected]> wrote: > +1. Most people are not doing compiles, we're trying to say that people live > in the web and in their browser, and that their browser is the primary > application. For me at least, that is true. The browser is the app I use the > most -- the only other app I use regularly is an ssh client, which can > usually fit in memory or get swapped back in much quicker than Chrome. > > 2009/6/23 Peter Kasting <[email protected]> >> >> FWIW, I strongly believe we should move the default to >> --memory-model=high. This is what pretty much every other app in the world >> does, and we mostly penalize ourselves when the OS aggressively swaps us out >> for a dumb reason (which yes, Windows does do). >> We have a lot of complaints of "I came back the next hour/day/whatever and >> everything was unresponsive". I don't think our current tradeoff is the >> right one. >> I know Mike wants to be a good citizen and feels like if the OS swapped >> you out it really needed that RAM, but in my own observations of my machine >> the OS swaps for retarded reasons and I gain nothing but headaches. >> PK >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
