I am willing to volunteer to be a test case if you need one, tell me what to do so you will be able to monitor.Before I added that switch, it was pretty horrible.
Though I am building stuff with Java, XSLT, JavaScript that process a lot of files (HTMLs) and viewing and refreshing a lot of pages (in Chrome, mostly, but sometimes in other browsers for cross browser support), plus Eclipse and Outlook, if it matters. ☆PhistucK On Wed, Jun 24, 2009 at 19:46, Mike Belshe <[email protected]> wrote: > > > 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. > > > > This doesn't make sense as a use case, because if there is nothing else > eating your memory, then the memory doesn't have to "swap in". It's already > there! :-) For users with plenty of RAM like you, memory-model=medium > should work just fine. > > The only people that might be effected by this is people that do have > something else competing for the memory (like a compile, or they are on a > low-memory box and outlook is eating it). > > I do worry that virus scanners could churn through memory causing similar > effects, but again, we measured for this and so far have been unable to > detect any difference. > > At this point we could change to memory-model=high, despite having no > real-world data that this is a problem. Chrome would be perceived to use > 25% more memory, and the folks on this thread that have compiles going might > feel a better experience. If we don't care about a 25% jump in memory use > then we should switch the default even though data suggests it won't help. > > One more possibility: maybe there is a bug we haven't yet identified. > > Mike > > > >> >> >> 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 -~----------~----~----~----~------~----~------~--~---
