Date: Fri, 31 May 2002 12:25:52 -0500
Reply-To: aldi <aldi@WUBIOS.WUSTL.EDU>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: aldi <aldi@WUBIOS.WUSTL.EDU>
Organization: Washington University in St. Louis
Subject: Re: out of memory problem:
Content-Type: text/plain; charset=us-ascii; format=flowed
Thank you Stanley for the input.
I do not think the problem I am referring to is the case as you brought
the example, although it is helpful to think.
My program is running in a server under SAS for Linux. 1GB mem, and 4GB
swap space. I tested memsize=600MB and still the error: out of memory is
there.
Here is the report, maybe someone had this problem before and found a
solution. (I know one, by separating processes into single variables,
but it looks to me as not a good solution. I have memory in the server
and also hardrive, why SAS is not expanding its work?). Can it be
possible that ODS is causing this problem of out of memory?
TIA,
Aldi
log report:
NOTE: Writing ODS PDF output to DISK destination
"/.users/genetics/aldi/segpower/mainsim1/UnivarBoxMix.pdf",
10 The SAS System
printer "PDF".
295 proc univariate data=mixed01.mixedsim;
296
297 var rep pedid subject p1 qn1-qn5 ql1-ql5;
298 title "Univariate in all data combined: mixed model";
299 run;
ERROR: Out of memory.
ERROR: Out of memory.
ERROR: Out of memory.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE UNIVARIATE used:
real time 11.41 seconds
cpu time 11.44 seconds
300
301 proc boxplot data= mixed01.mixedsim;
302
303 plot p1*rep;
304 title "Boxplot on p1 dependent variable: mixed model";
305 run;
NOTE: Processing beginning for PLOT statement number 1.
NOTE: There were 600000 observations read from the data set
MIXED01.MIXEDSIM.
NOTE: PROCEDURE BOXPLOT used:
real time 13.60 seconds
cpu time 2.00 seconds
Gorodenski, Stanley wrote:
> We had an interesting situation at work where my employee could not get proc
> summary to work. We have WindowsNT running on a Novell network. It turned
> out that his system loaded Microsoft Office and Fast Find. This caused a
> memory problem for SAS and when these were deleted from the task list it
> enabled SAS to get to the next problem which was not enough disk space. When
> these were taken care of, his SAS program ran okay.
>
>
>>-----Original Message-----
>>From: aldi [mailto:aldi@WUBIOS.WUSTL.EDU]
>>Sent: Friday, May 31, 2002 7:19 AM
>>To: SAS-L@LISTSERV.UGA.EDU
>>Subject: out of memory problem:
>>
>>
>>Hi,
>>I see explanations on memsize and memleave in the SAS
>>manuals, but I am
>>not clear on the possible memory set.
>>Ok! I have a set with 600 000 observations, a set of 96MB in
>>size. I am
>>running a proc boxplot and SAS is reporting out of memory.
>>
>>Real memory of the system: 1GB. Based on the manuals the memsize by
>>default is 512KB. We have set it to 30MB. So I will go and define
>>memsize=100MB, but is there any rule of thumb how to define the
>>necessary memory?
>>TIA,
>>Aldi
>>
>