chari@nueces.cactus.org (Chris Whatley) (11/11/89)
Can somebody explain the ENOURMOUS process sizes on the NeXT. It is simply amazing how large things can get. My lpd is 16.5 megs! Chris -- Chris Whatley Work: chari@pelican.ma.utexas.edu (NeXT Mail) (512/471-7711 ext 123) Play: chari@nueces.cactus.org (NeXT Mail) (512/499-0475) Also: chari@emx.utexas.edu
avie@wb1.cs.cmu.edu (Avadis Tevanian) (11/12/89)
In article <1989Nov11.064549.18374@nueces.cactus.org> chari@nueces.cactus.org (Chris Whatley) writes: >Can somebody explain the ENOURMOUS process sizes on the NeXT. It is >simply amazing how large things can get. My lpd is 16.5 megs! Yes, all virtual sizes on a NeXT include the stack size that the process has asked for. In the case of lpd, it has a 16 meg stack. Shared libraries also add a few hundred K. In all of these cases, these are virtual sizes. So they often don't consume any physical resources, or as in the case of shared libraries, shared resources with other processes. -- Avadis Tevanian, Jr. (Avie) Manager, System Software NeXT, Inc. avie@NeXT.COM