Architecting, installing and maintaining your SAS environment

Object Spawner Major (page) Faults in the SAS Environment Manager

New Contributor
Posts: 3

Object Spawner Major (page) Faults in the SAS Environment Manager

Hi Admins, I do see, "Object Spawner Major (page) Faults" Alert in the SAS Environment Manager. Description: Major Faults are page faults requiring disk activity. Possible indication of a memory constraint causing slow performance. How do I fix this alert, increasing Heap size might help. But I would like to know are there any downstream impact by doing that.
Super User
Posts: 10,237

Re: Object Spawner Major (page) Faults in the SAS Environment Manager

Since the spawner (along with the metadata server) is usually started with the ID of the SAS installation user, I'd check the constraints of that userID.

OTOH, you might have developed a memory leak. See how long the spawner has been up, and stop/start it. You might consider to set up a periodic restart (eg every night).


With processes where only a single instance will be started on a given machine, you can be liberal with regards to memory consumption, while processes with many instances (workspace servers) should have settings that make sure all expectable concurrent instances fit into available memory.

Maxims of Maximally Efficient SAS Programmers
How to convert datasets to data steps
How to post code
Trusted Advisor
Posts: 1,789

Re: Object Spawner Major (page) Faults in the SAS Environment Manager

Hello @rsasb,


normally, that kind of a message is just a reflection of other problems, normally caused by the amount , the frequency or the duration of certain sessions. Or its incapability to close orphaned SAS sessions.


An example: Often, this is caused by long stored process sessions, or amount of spanwed STP sessions, which are meant to have short duration. The solution for those is to extend the pool of STP and improve the code for the Stored Processes, or memory settings.

Another example: if object spawner is incapable of closing orphaned SAS Workspace Server sessions, then it has to handle unuseful SAS sessions.

There are many more. I suggest to investigate the behaviour of your spawned SAS sessions. It is very rare the requirement to extend the memory settings of the SAS Object Spawner, even on really BIG deployments. It is a service very optimised.



Ask a Question
Discussion stats
  • 2 replies
  • 3 in conversation