[comp.windows.news] size of X vs. NeWS

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/09/90)

I performed the following experiments on a SPARCstation 1 with CG3:

    1. Started up xnews in NEWSONLY mode, two psterms, and a roundclock.
    2. Started up R4 Xsun, a twm, two xterms, and an oclock.

(xnews comes up with an internal wm, and roundclock ends up internal too.)
(oclock is a true oval clock; R4 supports nonrectangular windows.)

Here are numbers, in kilobytes, using size(1) for TEXT and ps(1) for DATA:

	TEXT   DATA                TEXT   DATA
xnews   1352   2628        Xsun     688    296
psterm    64     64        xterm    120    176
psterm           64        xterm           176
                           twm      152    100
                           oclock    80     32

I'm not sure how to measure shared library sizes, here's what size(1) says:

			   libX11   176
			   libXt    200
			   libXmu    48


	TEXT   DATA                TEXT   DATA
Totals: 1416   2756                1464    780

(Some portion of the xnews text should be subtracted as X specific.)

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/09/90)

[Corrections from the previous message:
    1. A GX was installed, not a CG3.
    2. I forgot to include the X widget library!
    3. I failed to include data sizes for the X shared libraries.
]

I performed the following experiments on a SPARCstation 1 with GX:

    1. Started up xnews in NEWSONLY mode, two psterms, and a roundclock.
    2. Started up R4 Xsun, a twm, two xterms, and an oclock.

(xnews comes up with an internal wm, and roundclock ends up internal too.)
(oclock is a true oval clock; R4 supports nonrectangular windows.)

Here are numbers, in kilobytes, using size(1) for TEXT and ps(1) for DATA:

	TEXT   DATA                TEXT   DATA
xnews   1352   2628        Xsun     688    296
psterm    64     64        xterm    120    176
psterm           64        xterm           176
                           twm      152    100
                           oclock    80     32

I'm not sure how to measure shared library sizes, here's what size(1) says:

			   libX11   176     24
			   libXt    200     48
			   libXmu    48      8
			   libXaw   152     40


	TEXT   DATA                TEXT   DATA
Totals: 1416   2756                1616    900

(Some portion of the xnews text should be subtracted as X specific.)

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/10/90)

    Are "psterm" and "xterm" comparable in functionality, or could
    functionality differences account for the difference in size between
    them, at least in part?

I don't have a good feel for comparing their functionality.  I suspect
xterm has more (generally useless :-) bells and whistles.

    Was "psterm" linked with any NeWS shared libraries?

ldd says it is only linked with libc.

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/10/90)

    How much of the XSUN size was server size? All of it?

Xsun *is* the X server.

    You should split the memory usage into server/client requirements, praps?

I thought that's what I did on the X side ...