Gaining Comfort with SAS Grid Computing for Analysts and Data Scientists video, slides, examples plus questions and answers are now available.
This session describes what SAS Grid Computing is and how can it boost your analytics' performance. It introduces you to the key concepts, benefits and techniques that you can use to gain the most efficiencies from SAS Grid Computing.
Here are some highlighted questions and answers that were submitted. Scroll down to review the attached slides.
Yes, you can run it as a procedure or invoke it via the program editor -> analyze -> analyze for Grid.
The before and after illustrations that were demonstrated were apples to apples; the procedural steps were first run sequentially on a 5 node SAS Grid Computing configuration, where they consumed 9+ minutes of real time. Those same procedural steps were respecified via SCAPROC to contain remote submits to process the procedural steps in parallel on the same a 5 node SAS Grid Computing configuration, where they consumed 2+ minutes of real time.
You can think of SAS Grid Computing as an extension of SAS/CONNECT where the Grid Control Server automates the processing. Not only can you run in parallel on the same box, you can also split the processing across multiple machines (nodes) because the job is submitted through the Grid Control Server. As you will see later in the webinar, you can analyze your SAS programs to determine if you can break it up into sessions, running the various steps in parallel.
You can monitor the job in the SAS Management Console and the LSF on-line tools to see which server node the job is running onAlso, you can use: %put %sysget(HOSTNAME); plus two grid macros %jobinfo; and %gjobs; - the node will show in the log from signon. You can also use %sysget to set up macro variables., or %SYSFUNC(GRDSVC_GETNAME(TASK1));
Yes, Windows and Unix are supported and they can be combined together http://support.sas.com/rnd/scalability/grid/SAS_Grid_FAQ_External_31JUL2007.pdf
You can see it in your library and folder lists in interfaces such as SAS Studio, Enterprise Guide, SAS Add-In for Microsoft Office, Enterprise Miner, etc. If you have been granted permission to see it in the SAS Management Console, you’ll also see it there.
Please check with your SAS administration team because they have ways to improve your SAS Grid Computing environment. You may also want to pursue a professional assessment and tune-up service
If you are looking for metrics via job and steps, CPU and memory by server:
Please be aware that this macro is only for SAS Grid Computing.
SCAPROC is a Base SAS procedure, so it runs the same way regardless of the host operating system(s).
1) add a WAITFOR statement in the code - easiest way for analysts to control this operation, especially for testing or ad hoc scenarios.
2) use schedule manager in SAS Management Console to schedule jobs to run with dependencies - a more strategic approach for production operations, will likely involve SAS administrators' participation.
Please explore SAS functions such as PUT and INPUT to conduct this conversion. There’s another on-demand Ask the Expert webinar on this topic https://communities.sas.com/t5/Ask-the-Expert/Top-10-SAS-Functions/ta-p/391244
It enables or disables one or all SAS sessions on a grid, so you’ll want to consider when and how many sessions to enable.
Analyze for Program will analyze your code and create a process flow of each step in the code. Analyze for Grid will assess and add the SCAPROC statements to your code for SAS Grid Computing.
When you analyze the SAS code using SCAPROC or submit by SASGSUB, the dependencies will be determined.
Yes, all those steps will run sequentially in the one grid session.