[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1481.0. "Decwindows on a 4 MB VAXstation 2000: Yes or No?" by SSDEVO::SHICK () Fri Sep 22 1989 20:14

    I have hunted haphazardly around in this notesfile and haven't seen
    anything that addresses my question and haven't had the time to read
    through the entire notesfile.  
    
    Is it possible to run decwindows on a VS2000 with 'only' 4 Meg?  I am
    running on an LAVC at VMS5.2 and tried it two weeks ago and completely
    locked up my system.  Is DW wonderful enough to be worth fooling with?
    

T.RTitleUserPersonal
Name
DateLines
1481.1LESLIE::LESLIEFri Sep 22 1989 20:415
    Official answer: just about.
    
    Unofficial answer: get additional memory - fast. I use 14mb and DW
    flies.

1481.2I think the official answer is "unsupported"VMSDEV::BALLOUIt's not slow, it's careful!Fri Sep 22 1989 21:0811
    Actually, I would take exception that the official answer is "just
    about."  I believe the official answer is "unsupported."  If you're
    going to be in a cluster, the minimum supported configuration is 6
    megabytes.  If you are going to run standalone, the minimum supported
    is 4 meg.
    
    On the other hand, it would take an awful lot of coaxing to get me to
    touch a 4 meg system running DECwindows, standalone or otherwise. :-)
    
    					- Ken

1481.3Not supported in a cluster or if you don't have another machineHANZI::SIMONSZETOSimon Szeto @HGO, HongkongSat Sep 23 1989 09:3422
    According to the V5.2 SPD, 4 meg is the minimum if you have DECnet and
    DECwindows with applications running remotely, 6 meg with applications
    running locally or in a cluster.  And the following note:
    
    "Note:  These memory requirements are the minimums. [sic]
            More memory will be required for satisfactory
            performance of the operating system and DECwindows
            applications.  The performance and memory usage of
            VMS DECwindows systems is particularly sensitive to
            system configuration and window and application
            usage.  Remote execution of an application requires
            an additional system which runs the application while
            the display of the application occurs on the local
            workstation."
    
    Yes, we have some 4 meg VS2000's running (so to speak) DECwindows.
    It's too bad our upgrade orders have been sat on because of budget
    (or lack thereof).
    
    --Simon
    

1481.4LESLIE::LESLIESat Sep 23 1989 16:407
1481.5DECwindows on a 6MB 2000...SPUDZ::HETTICHMiss PurpleSat Sep 23 1989 22:2511
    I have DECwindows running on a 6MB 2000, with the bare essentials. 
    I boot off a local area VAXcluster, and I have found the most efficient
    way to run windows (with anything other than 1 DECterm window on my
    2000) is to simulate a "SET DISPLAY" off one of the main nodes in the
    cluster...even with this I sometimes run with 100 or less free pages...
    can't imagine how you could run DECwindows with 4MB.
    
    Cathy
    
    

1481.6Discussion here doesn't apply to customersSDSVAX::SWEENEYI was focused when focus wasnt coolMon Sep 25 1989 11:2311
    A general point to be made about questions regarding "support":

    Even if your question is "just for your own information", others
    reading this conference or any other, are likely to regard it as
    authoritative for communication to customers.

    What constitutes "support" as far as customers are concerned is spelled
    out in the Software Product Description.  In my experience, SPD's tend
    to be free of Digital's usual ambiguity.  In any case, interpretations
    of SPD's come from CSSE and Product Mgmt.

1481.7We run a lot of 6MB VS2000's hereASHBY::FEATHERSTONEd FeatherstonMon Sep 25 1989 12:097
With all applications running remotely, and by forcing swapping on the VS2000
(set BALSETCNT low). This gives the server and window manager enough memory
for reasonable performance. All the VS2000's are in a VAXCluster. I don't 
think I would attempt it with anything less than 6MB though.

				/ed/

1481.8KONING::KONINGNI1D @FN42eqMon Sep 25 1989 15:287
One suggestion I've heard:  Run ELN on the workstation, and pretend it's
an X Terminal.  I don't know how that would compare with anything else
you could do given the current memory situation, but it might be worth
a try.

	paul

1481.9CHEESE::KAISERMon Oct 02 1989 00:2011
> One suggestion I've heard:  Run ELN on the workstation, and pretend it's
> an X Terminal.

To elaborate a little for those who never need touch realtime: VAXELN is our
toolkit for realtime or dedicated applications; it runs on VS2000s (and up),
and as of the latest release includes DECwindows.  With at least one customer
I've been so rash as to suggest they might want to take .-1's suggestion as a
way of milking the last iota of usefulness out of their VS2000s.  Was I wrong?

---Pete

1481.10PAXVAX::MIANOWelcome to Boston! Now, go home.Mon Oct 02 1989 02:5021
    >With at least one customer I've been so rash as to suggest they might
    >want to take .-1's suggestion as a way of milking the last iota of
    >usefulness out of their VS2000s.  Was I wrong?
    
    No, you're not wrong. Because of the cost of memory upgrades, there are
    several customers thinking about this sort of thing right now (that I
    know of). 
    
    As you may or may not be aware, it doesn't matter in VAXELN whether you
    have 4 MB or 40 MB -- since there's no paging or swapping in and out of
    memory, there is no performance increase in getting more memory. As
    long as the actual code can fit into available memory and has enough
    room left over to run, you're all set. In 4MB you can fit the server
    and then maybe a couple good size applications (or 1 monster application
    like the DECwindows window manager). Then, if that's not enough, you can
    start a whole bunch more of your favorite applications from somewhere
    else.
    
    If your customer has severe cost limitations, it doesn't even need a
    disk. This is a completely stand-alone diskless DECwindows environment.