Desktop productivity for business analysts and programmers

User memory limitation

Reply
New Contributor
Posts: 3

User memory limitation

Is it possible to limit memory by user? We need to modify the default settings for each session in the Workspace Server. We have several users, and also have default users (sasdemo, sassrv) running.

 

Our matter is to specify differents 'memsize parameters' fot the two different group of users. We have tried to change the properties in sasv9.cfg, sasv9_usermods.cfg and Workspace_usermods.sh, however, were not successful.

 

Anybody could help us?

 

Thanks in advance,

kind regards.

Trusted Advisor
Posts: 1,197

Re: User memory limitation

Hello,

 

it is definitely possible. For that you need to create a new SAS Application Server (SASApp) with different name (if you hace SASApp, name the new one as SASAppExt or similar), with a Workspace Server. On the new SASApp you can put the different memory settings.

Then, the last thing you will need to do, is to assing the required libraries to the new SASApp server too and assign authorizations to users to access one SASApp server or the other one or both.

Super User
Posts: 5,388

Re: User memory limitation

That will limit the resource per session, a user could have multiple sessions active at the same time.
Data never sleeps
Super User
Posts: 3,237

Re: User memory limitation

What is your ultimate goal? To reduce memory usage on your SAS App server or something else? This has to be handled carefully as users could suddenly find that their memory-intensive jobs fail. While a memsize of 2G is good for most users, I've had jobs fail unless they have 3GB.

 

Also memory is quite cheap so why not upgrade your server memory? Another approach might be to limit the maximum number of simultaneous SAS sessions a user has.

New Contributor
Posts: 3

Re: User memory limitation

Actually, our ultimate goal is only to limit sas-sessions by memory, because we have installed SAS Marketing Automation and need enough memory space for the SAS Customer Intelligence sessions. SAS CI Studio is our priority and we do not wish grant a privilege to SAS Enterprise Guide users.

 

 

Trusted Advisor
Posts: 1,197

Re: User memory limitation

[ Edited ]

Yes, I guessed that much, it is a common practice on several CI deployments.

As mentioned, I think your best approach would be to have 2 SASApp servers (at least): one for CI only (which also probably is on UTF-8,unicode as locale), where you can set higher resource limits, and another one for your SAS EG users (or Addin, etc), with lower resource limits per session. Which you can do with MEMSIZE, CPUCOUNT, MAXMEMSZ, etc.

New Contributor
Posts: 3

Re: User memory limitation

Yes, I think this could be a good option and finally, will be applied. However, I would like to try another solution. My PM insists that we could limit the memory-size sessions modifying the parameters in the SAS configuration files (i.e., sasv9.cfg or sasv9_usermods.cfg), for each OS user in their home directories.

 

What do you think about that? Could it be a suitable solution?

 

Thanks in advance.

Trusted Advisor
Posts: 1,197

Re: User memory limitation

[ Edited ]

If you manage to assign dinamically the SAS Workspace's sasv9.cfg by user home folder without impacting on the SAS Workspace's sasv9.cfg for CI, it would sound as a reasonable option to me. Beware that if you select this option, your maintenance efforts will increase with a multiplier equals to the number of users.

 

My option would be, still, to have 2 separate SASApps, because of several reasons and it is good practice. But my option does not have to be yours!

 

If you do it on this way, please share your implementation Smiley Happy

PROC Star
Posts: 1,146

Re: User memory limitation

I vote with Juan, myself. Note his comment about the additional work having to modify each home directory. Also, what stops me as a knowledgeable SAS user from resetting my memory limit to whatever I want?

 

Tom

Ask a Question
Discussion stats
  • 8 replies
  • 671 views
  • 0 likes
  • 5 in conversation