ADSM-L

Re: Netware client Memory problem ?

1995-06-21 14:07:55
Subject: Re: Netware client Memory problem ?
From: "Yves Le Tremblay" <YTREMBLAY AT NESTOR.SI.USHERB DOT CA>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 21 Jun 1995 13:07:55 EST
Date d'envoi:   Thu, 15 Jun 1995 09:51:04 PDT
Repondre a:     "Dist. Stor. Manager(ADSM) List" <ADSM-L AT VM.MARIST DOT EDU>
De:             Frank Ramke <ramke AT VNET.IBM DOT COM>
Sujet:          Netware client Memory problem ?
A:              Multiple recipients of list ADSM-L <ADSM-L AT VM.MARIST DOT EDU>

>................I think that there's change in release 1.2.8 with the
> performance and memory allocation. Is a real proble with ADSM client or
> i must set options in dsm.opt to free memory after backup.

The change was to use memory from the Large Non-movable memory pool. The
memory is freed by ADSM after running the operation.
There is no option for freeing memory after the operation,
it is done automatically. The memory is returned
to the system for file caching. Using monitor.nlm, you can watch the
memory allocations for the system and/or each running module in the
system. I have been informed of NWSAA using lot's of short term memory.
Are you using this product?

Try "set maximum alloc short term = 16", if you're running 3.12 server
and NWSAA.

I Frank, All my netware client are 1.2.8 or 1.2.7. Since i migrate
these users from ADSM VM server to ADSM6000 server , all my netware
client are this problem. Some client use the same client release and
haven't problems of memory if they use the ADSM VM server, and has
the memory problem with ADSM6000 Server....
                                           Yves
<Prev in Thread] Current Thread [Next in Thread>