12 Oct
2000
12 Oct
'00
11:36 a.m.
From: healyzh(a)aracnet.com <healyzh(a)aracnet.com>
Beware, I found that it was painful to run Netscape on a Tru64 system
with
96MB. Tru64 seems to be even more of a memory pig than
OpenVMS.
VMS isn't a memory pig. Alpha however was aimed at big apps and isn't
as byte efficient as VAX so it tends to consume 2x-4x the ram. The
design
goal of Alpha was big address space for even bigger apps like gigabyte
or even terabyte sized databases.
A VAX with 64-128 mb is a big (memory wise) machine. Besides 7.2 runs
just fine in the MVII with 9mb!
Allison
12 Oct
12 Oct
1:03 p.m.
Allison wrote:
From: healyzh(a)aracnet.com <healyzh(a)aracnet.com>
I think you know what I mean :^) The system in question is an Alpha, and on
Alpha's OpenVMS is a memory pig! A quick (SHO CLUS) shows that my 24MB
VAXstation 4000/VLC is sitting at 60% memory usage, the AlphaStation 500/333
with 96MB that doesn't have DECwindows loaded on the system is sitting at
69%, unfortunatly I don't have either of the workstations with 112MB up at
the moment as but running DECwindows I believe they'll be at about 80%,
IIRC. Of course my main system is only at 20% :^)
I understand why OpenVMS on an Alpha uses so much memory as opposed to on a
VAX, however, the fact remains, it's a memory hog, and like I said based on
my very limited Tru64 experience it seems even worse on the exact same
hardware.
Zane
Beware, I found that it was painful to run
Netscape on a Tru64 system
with
96MB. Tru64 seems to be even more of a memory pig
than OpenVMS.
VMS isn't a memory pig. Alpha however was aimed at big apps and isn't
as byte efficient as VAX so it tends to consume 2x-4x the ram. The
design
goal of Alpha was big address space for even bigger apps like gigabyte
or even terabyte sized databases.
A VAX with 64-128 mb is a big (memory wise) machine. Besides 7.2 runs
just fine in the MVII with 9mb! 
14 Oct
14 Oct
10:57 p.m.
At 18:03 12/10/00 -0700, healyzh(a)aracnet.com wrote:
I think you know what I mean :^) The system in
question is an Alpha, and on
Alpha's OpenVMS is a memory pig! A quick (SHO CLUS) shows that my 24MB
VAXstation 4000/VLC is sitting at 60% memory usage, the AlphaStation 500/333
with 96MB that doesn't have DECwindows loaded on the system is sitting at
69%, unfortunatly I don't have either of the workstations with 112MB up at
the moment as but running DECwindows I believe they'll be at about 80%,
IIRC. Of course my main system is only at 20% :^)
I understand why OpenVMS on an Alpha uses so much memory as opposed to on a
VAX, however, the fact remains, it's a memory hog, and like I said based on
my very limited Tru64 experience it seems even worse on the exact same
hardware.
Have you done any tuning on the system? The default values of some of the
SYSGEN parameters are set in such a way to protect less knowledgeable
customers from themselves. At the very least use AUTOGEN with feedback to
see if the report generated indicates a few parameters that could be
downsized. I'm not near a running VMS system right now (restructuring my
home office/computer room and the VMS systems are in pieces down the
corridor) so all of this is coming from memory but something like
$ @SYS$UPDATE:AUTOGEN GETDATA GENPARAMS FEEDBACK
will generate a report file (SYS$SYSTEM:AGEN$PARAMS.REPORT) and not do
anything to the system.
Huw Davies | e-mail: Huw.Davies(a)kerberos.davies.net.au
| "If God had wanted soccer played in the
| air, the sky would be painted green"
8835
days inactive
8838
days old
2 comments
3 participants
participants (3)
-
ajp166＠bellatlantic.net -
healyzh＠aracnet.com -
Huw.Davies＠kerberos.davies.net.au