On Sun, Jun 21, 2009 at 12:37 AM, n179911 <[email protected]> wrote: > > Hi, > > There is a test which compares memory usage among rendering engines > http://dotnetperls.com/chrome-memory > > From the site, it shows the maximum memory usage of Chrome is more > than Safari is > 2 times. > Since both of them are Webkit base, does that mean the V8 engine uses > twice as much memory as squirrel fish?
No. Chrome's multi-process architecture means that each renderer runs in its own Javascript heap. When you start up any browser, the JS engine will allocate some amount of memory to its heap. It will garbage collect under some policy (such as when it reaches certain size limits). In this case, chrome has 30 processes, and thus 30 javascript heaps. Since the test just hits home pages, each heap is probably fairly small. If you wanted to compare Squirrelfish to this test, you'd have to create 30 instances of it :-) Anyway, if you want to compare V8 to SquirrelFish, there are better ways to do it (you can take the browser out completely and run tests using each JS engine's command line shell). You'll find that V8's heap is very compact. The problem demonstrated in this site's test has more to do with how Chrome behaves with multiple processes than it does with Javascript. I also think that the overall performance and reliability benefits of the multi-process architecture far outweigh the memory impacts. And this test, IMHO, is not very close to a realistic test of what users do. Mike > > > > > --- Maximum memory used --- > Peak memory usage measured during experiment. > > Chrome: 1216.16 MB [Largest] > Firefox: 327.65 MB [Smallest] > Opera: 554.11 MB > Safari: 517.00 MB > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
