Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!CAD.USNA.MIL!dfr
From: dfr@CAD.USNA.MIL ("David F. Rogers")
Newsgroups: comp.sys.sgi
Subject: windows
Message-ID: <8905170942.aa09286@CAD.USNA.MIL>
Date: 17 May 89 13:42:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 30

G'day Mark,

I may even antedate you with SGI. As I recall the first 2400 that I bought
did not have a window manager at all, i.e., no mex.

Since I have raised the question, what does not someone at SGI sit down
and provide a concise, definitive answer to:

1. how much memory does the current window manager system use -- say with
one window. How much additional memory for each additional window?

2. How much cpu power does the window manager absorb -- say with one window.
How much for each additional window or task, e.g. mouse input, keyboard input,
etc.

3. How can you absolutely minimize the effect of the window manager?

The thing that really concerns me here is that I demonstrated that the
new machine was not VISUALLY as fast as a 2400T. In real time interactive
systems it is VISUALLY that counts.

Professor David F. Rogers
Aerospace Engineering Department
U.S. Naval Academy
Annapolis, MD 21402
USA
Tel: 301-267-3283/4/5
 
ARPANET: dfr@usna.navy.mil
UUCP:    ~uunet!usna!dfr