I suspect a big chunk of the memory is the V8 heap. Each process that uses V8 will need a separate heap. We could experiment with lowering the heap size for extensions, if we think extensions will be less script heavy than web pages.
On Fri, Jul 10, 2009 at 5:37 PM, Erik Kay <[email protected]> wrote: > As we add more subprocesses (workers, utilities, extensions, etc.), it > would be great if we could reduce the minimum memory that these processes > consume. I know that there was some work done a while back to look at what > was the minimum cost of a new process on Windows given our dll size, etc. > (maruel?), but I'm sure that there's more than can be done for us to reduce > memory usage above this level. > Erik > > > On Fri, Jul 10, 2009 at 1:03 PM, Paweł Hajdan Jr. <[email protected] > > wrote: > >> >> As extensions are visible in the task manager, it's also possible to >> see their memory usage. I was experimenting with some sample >> extensions, and the usage seems to be in range 1 MB - 12 MB. Typically >> 3-5 MB. >> >> I wonder if it would be possible to reduce that memory usage. In case >> it negatively affects performance, we could have some opt-in way for >> extension developers to say "I want my extensions to run as fast as >> possible, even with increased memory usage". >> >> What do you think? >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
