Getting Started Documentation Glish Learn More Programming Contact Us
Version 1.9 Build 392
News FAQ
Search Home

next up previous
Next: Discussion Up: Memory Use Previous: Memory Allocations

Executable Sizes

AipsView is about 1.4M (shared X libraries). Glish and a client or two should be 5M or less (shared Glish libraries). Imager is 10M.

While the Glish size seems a little large (statics?), Imager is clearly the largest offender. Presumably this is largely caused by template instantiations of similar functions.

Moreover, unless common library functionality is in a shared library, this bloat will add up linearly with the number of processes.4. Moreover, large executable sizes imply slow startup of the executables if they must be fetched over the network (for example, via NFS).

next up previous
Next: Discussion Up: Memory Use Previous: Memory Allocations
Please send questions or comments about AIPS++ to aips2-request@nrao.edu.
Copyright © 1995-2000 Associated Universities Inc., Washington, D.C.
Return to AIPS++ Home Page
2004-01-31