git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RAM consumption when working with the gcc repo

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 8, 2007, 11:54 UTC
Message-ID
<Pine.LNX.4.64.0712081153500.27959@racer.site>
In-Reply-To
<e5bfff550712071325k3d4dadf2gf34c069022cc005@mail.gmail.com>
Hi,
On Fri, 7 Dec 2007, Marco Costalba wrote:
Show 10 quoted lines
> On Dec 7, 2007 9:46 PM, Nicolas Pitre <nico@cam.org> wrote:
> >
> > The other 2.3GB is hard to explain.
> 
> BTW does exist a tool to profile memory consumption by each source level 
> struct / vector/ or any other data container?
> 
> Valgrind checks mainly memory leaks, callgrind gives profiling 
> information in terms of call graphs and times/cycles consumed by each 
> function.
Have you looked at Massif (also part of Valgrind)?

Ciao, Dscho

Previous: Marco CostalbaNext: Marco Costalba
Message 7 of 15 in “RAM consumption when working with the gcc repo”
  1. Jon SmirlDec 7, 2007
  2. david@lang.hmDec 7, 2007
  3. Marco CostalbaDec 7, 2007
  4. Nicolas PitreDec 7, 2007
  5. Jon SmirlDec 7, 2007
  6. Marco CostalbaDec 7, 2007
  7. Johannes SchindelinDec 8, 2007
  8. Marco CostalbaDec 8, 2007
  9. Jon SmirlDec 7, 2007
  10. Jon SmirlDec 7, 2007
  11. Jon SmirlDec 7, 2007
  12. Martin KoeglerDec 8, 2007
  13. Jeff KingDec 7, 2007
  14. Jeff KingDec 7, 2007
  15. Jon SmirlDec 7, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.