SAS Data Integration Studio, DataFlux Data Management Studio, SAS/ACCESS, SAS Data Loader for Hadoop and others

SAS LASR Memory Alternatives

Reply
Occasional Contributor
Posts: 9

SAS LASR Memory Alternatives

I need help regarding SAS memory management, currently I have 96 GB LASR memory but my production data base size is huge so currently we put only 90 days data (only important table) in SAS LASR, now LASR memory is almost full and due to this SAS server is goes down so many time, due to this all data is truncated from memory, so can you suggest me how manage SAS memory system or save data in disk other than LASR or opimization of data in LASR, any best way optimize data size of table

 

 

proc sql ;
connect to odbc (dsn=inventory user=ashu password='');  
create table libname.test_table as select
c0  format=11.,
c1  format=$30. length=30,
c2  format=11.,
c3  format=11.2
from connection to odbc
(SELECT c0,c1,c2,c3
FROM db_name.test_table
limit 10Smiley Wink;
disconnect from odbc;
quit ;

 

Super User
Posts: 5,257

Re: SAS LASR Memory Alternatives

Save data on disk removes the possibility to (immediately) analyze it in VA/VS. So it depends hon your whole analytical environment/process if that's feasible.

 

There a few techniques (not limited to) that can save memory in LASR, what to do depends on your data, requirements and query patterns:

  • Compress
  • Star schema
  • Truncate char cols
  • Use formats
Data never sleeps
Respected Advisor
Posts: 3,896

Re: SAS LASR Memory Alternatives

[ Edited ]

I don't have practical experience with it but it appears the 2.4 version got a squeeze option which allows for compressed in-memory tables.

http://support.sas.com/documentation/cdl/en/inmsref/67597/HTML/default/viewer.htm#inmsrefwhatsnew24....

 

Super User
Posts: 3,112

Re: SAS LASR Memory Alternatives

Compression is available in the more recent versions of SAS VA, but the down side is it can have a very significant impact on performance and needs to be used with extreme caution. For large tables like the one being discussed it could be a total CPU killer. Have a look at the other options suggested first.

 

Also if you don't need row-level detail in VA consider pre-summarising your data first to reduce the size.

Ask a Question
Discussion stats
  • 3 replies
  • 296 views
  • 1 like
  • 4 in conversation