Memphis still says Calculate is taking 10 MB, which compared to the RAM in a "physical" calculator is quite a lot.
Also, e.g. Memphis is attributing 110 MB to Squeak, when most of that is unused virtual address space (which "top" actually gets right). - Bert - On Sep 18, 2007, at 13:53 , Jim Gettys wrote: > Bert, > > Don't confuse virtual address space used with RAM consumed: most of > that > is shared memory (glibc, pango, gtk+....). > > That's why memphis was written and is in our build: ps gives very > misleading memory usage statistics, unless you really understand > what it > is reporting. It does a bit better job accounting for memory used > in a > mere-mortal way to understand. > > Even so, right now we'll find lots more RAM consumed that we'd > like, due > to how python loads modules; we have schemes for fixing this using > fork > and copy on write. > - Jim > > > On Tue, 2007-09-18 at 11:30 +0200, Bert Freudenberg wrote: > >> >> Well, if the XO's calculator activity can take 20 MB RAM (+10MB >> shared), then 2 MB for a clock seems small. >> >> - Bert - _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
