09-07-2016 02:32 PM - edited 09-07-2016 02:33 PM
We have been testing and load balancing our Grid in our TEST environment before going to PROD and it doing we discovered something odd with the way SAS Studio behaves with GRID. As a note we are using Grid-Launched Workspace Servers.
When we tested GRID with EG we noticed that SAS will spin up 1 job slot on GRID, which is fine as this is expected behavior; however, with SAS Studio we are seeing two job slots being occupied when SAS Studio starts. We have watched the process with bhosts and bqueues and made sure that it is consistently happenening.
Has anyone seen or had this happen to them in their environment?
Side-note: I was the only one in the environment when I was producing/re-producing this behavior so I know that one SAS Studio Session causes 2 job slots to be occupied.
09-08-2016 04:49 AM
SAS Studio uses two SAS process in the back. One services the code submission & one services the interface (file, folder, library operations, etc.)
09-08-2016 08:19 AM
whenever you'd like to get information about services, servers etc running in your environment, you could use
SAS Environment Manager to look at it, monitor it.
for general info on the Environment Manager.