T.R | Title | User | Personal Name | Date | Lines |
---|
1481.1 | | LESLIE::LESLIE | Andy ��� Leslie | Fri Sep 22 1989 17:41 | 5 |
| Official answer: just about.
Unofficial answer: get additional memory - fast. I use 14mb and DW
flies.
|
1481.2 | I think the official answer is "unsupported" | VMSDEV::BALLOU | It's not slow, it's careful! | Fri Sep 22 1989 18:08 | 11 |
| 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.3 | Not supported in a cluster or if you don't have another machine | HANZI::SIMONSZETO | Simon Szeto @HGO, Hongkong | Sat Sep 23 1989 06:34 | 22 |
| 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.4 | | LESLIE::LESLIE | Andy ��� Leslie | Sat Sep 23 1989 13:40 | 7 |
| re: .2 I take exception to your exception. Please note that the text
of the current SPD, as quoted in .3 (thanks Simon) can be reduced very
satisfactorally to "just about supported", possibly with the addition
of "but don't expect to DO anything".
- ���
|
1481.5 | DECwindows on a 6MB 2000... | SPUDZ::HETTICH | Miss Purple | Sat Sep 23 1989 19:25 | 11 |
| 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.6 | Discussion here doesn't apply to customers | SDSVAX::SWEENEY | I was focused when focus wasnt cool | Mon Sep 25 1989 09:23 | 11 |
| 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.7 | We run a lot of 6MB VS2000's here | ASHBY::FEATHERSTON | Ed Featherston | Mon Sep 25 1989 10:09 | 7 |
| 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.8 | | KONING::KONING | NI1D @FN42eq | Mon Sep 25 1989 13:28 | 7 |
| 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.9 | | CHEESE::KAISER | | Sun Oct 01 1989 22:20 | 11 |
| > 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.10 | | PAXVAX::MIANO | Welcome to Boston! Now, go home. | Mon Oct 02 1989 00:50 | 21 |
| >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.
|