Are there any specific settings to add in sasv9_local.cgf for SAS VA Non Distributed? Some of the settings we added are below but these are typical settings for all SAS applications not just VA. I am curious to know if there are any specific options we can add for SAS VA.
-VALIDVARNAME ANY
-WORK
-MEMSIZE
-SORTSIZE
-WORKPERMS
-UTILLOC
-FULLSTIMER
You need to properly adjust MEMSIZE. With the default value, you won't be able to load more than 2G of data.
Thank you Alexal. Are there anything besides memsize? Anything related to autoload, etc... that we need to add into sasv9-local?
Nope, but if you are using the autoload process to start the LASR server, do not forget to adjust MEMSIZE in AutoLoad_usermods.cfg. This is important.
Ok. Great. Thank you for your prompt response.
Are there any recommendation for MEMSIZE? For now I set it to 1GB. I am sure it all depends on the volume of data but still if there is something recommended by SAS let me know.
No, we do not have specific recommendations but 1GB is very low. By default MEMSIZE is 2GB. You need to be very careful with setting MEMSIZE, just do not forget that this option applies to all SAS sessions. So for an example, if you do "MEMSIZE 0", anyone who starts SAS session can consume all memory on the server.
Hello @Matt,
I strongly recommend you to read this article posted by @ErwanGranger : https://communities.sas.com/t5/SAS-Communities-Library/It-s-the-memsize/ta-p/239224
@alexal mentioned:
No, we do not have specific recommendations but 1GB is very low. By default MEMSIZE is 2GB. You need to be very careful with setting MEMSIZE, just do not forget that this option applies to all SAS sessions. So for an example, if you do "MEMSIZE 0", anyone who starts SAS session can consume all memory on the server.
On that note, I would like to comment that:
The MEMSIZE system option limits the total amount of memory that is available to each SAS session. It places an enforced limit on the amount of virtual memory that SAS can dynamically allocate at execution. If MEMSIZE is set too low, your jobs can fail, and errors appear in the SAS log indicating that insufficient memory was available. By contrast, the REALMEMSIZE and MAXMEMQUERY system options, the SORTSIZE= option in the SORT procedure, and the SUMSIZE= option in the SUMMARY procedure all provide for procedure tuning.
You have been properly advised to set up MEMSIZE, SORTSIZE is another good one to take care carefully regarding performance. Depending on your data and queries, just a megabyte of difference can create a difference of several seconds or even minutes in your VA reports.
As @ErwanGranger mentioned, the general advise is just to do as below. If you need posterior fine tuning, you can always contact SAS Technical Support (or your SAS representative) or an specialised partner on SAS deployments:
……./config/Lev1/SASApp/WorkspaceServer/WorkspaceServer_usermods.sh
This file, in VA environments should contain:
USERMODS_OPTIONS="-memsize 0 -cpucount ACTUAL "
Thank you. Will surely review the note.
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.
See how to use one filter for multiple data sources by mapping your data from SAS’ Alexandria McCall.
Find more tutorials on the SAS Users YouTube channel.